Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

MCP: expose span status and status message in inspect_span

Aperta
  • Qualcosa non va?
#1,873 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, observability

Direzione di ricerca

Start by reading packages/domain/src/mcp-outputs/traces.ts to compare TraceSpanOutput, which already carries status, against InspectSpanOutput, which does not. Then follow apps/ai/src/mcp/tools/inspect-span.ts for the handler and renderer, using apps/ai/src/mcp/lib/render-trace.ts as the rendering reference; check whether the span-detail query already selects statusCode/statusMessage before extending it. Done looks like structured and text output showing Unset, Ok, and Error distinctly, agreeing with inspect_trace, plus tests for error-with-message, error-without-message, Ok, Unset, and missing span.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

An agent inspecting one span cannot read its explicit OpenTelemetry status from inspect_span. The tool returns span attributes, resource attributes, and an optional AI decode, but its output schema and renderer omit statusCode and statusMessage.

A Worker can catch a failed operation, mark its custom span as an error, and still return a successful HTTP response. An agent needs that span status to understand the operation's result. Currently it must fetch inspect_trace separately, which already exposes these fields.

Why this matters for Cloudflare now

Cloudflare's October 26, 2026 Workers tracing update adds span.setStatus() to native custom spans. The explicit status and optional error message are included in exported OTLP traces, while the Workers Observability dashboard does not yet show span status.

This makes the existing MCP output gap more useful to close. The feature should work for spans from all OpenTelemetry producers.

Current code

Checked against main at 7edfccb17c3f524f9d793e0a11893fcf0535737e:

Proposed change

Expose the stored statusCode and statusMessage in both the structured and text results of inspect_span. Keep existing attributes, AI decoding, and missing-span behavior. Extend the span-detail query if needed.

Keep HTTP response status and OpenTelemetry span status separate. Do not infer an explicit Ok from a missing or unset status.

Acceptance criteria

  • inspect_span returns and renders the stored status and error message for a found span.
  • Unset, Ok, and Error remain distinct and agree with inspect_trace for the same span.
  • A custom span marked Error remains visible as failed even when the enclosing HTTP request succeeds.
  • Tests cover an error with a message, an error without a message, Ok, Unset, and a missing span.
  • Include a native Workers OTLP fixture using setStatus({ code: "error", message: "Probe failed" }), or verify the same path with a small Worker export.

Evidence: source inspection. A live Cloudflare-to-Maple export has not been tested for this report.

Lingua principale
TypeScript
Stelle
1.8k
Fork
120
Merge medio
8h 11m
PR unite (30g)
667

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MapleTechLabs/maple

Tutte le issue di MapleTechLabs/maple

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.