Skip to content

MCP: how to record params and result #3123

@lmolkova

Description

@lmolkova

Extracted from #2083 (comment). Need to decide how to record them

  • we record some of the params as dedicated attributes, e.g. mcp.resource.uri - should we record all of them as such?
  • we can record params one-by-one assuming they are orthogonal (e.g. mcp.input.param.location = Seattle, WA) or as a single complex attribute. It really depends on the usage pattern and whether people want to query by individual params
    • params._meta contain some things like progress report token that might not be interesting on telemetry
    • users might want to record some params/result but not all of it, instrumentations might support it via config in both cases (single params/result attribute vs multiple)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    New issues

    Status

    Need triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions