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

Preserve native JSON types when passing arguments to tool handlers

Aperta
  • Qualcosa non va?
#587 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
php
Ambito
backend-api-design

Direzione di ricerca

Start by tracing how validated arguments are passed to tool handlers and review the related decoding work in issue #586. Check the tests covering nested JSON values and handler arguments to identify where objects are converted to associative arrays. Done means handlers receive recursive stdClass, array, and scalar values as specified, with tests confirming the behavior.

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

Descrizione

enhancement
Is your feature request related to a problem? Please describe.

The SDK currently converts JSON objects into associative PHP arrays before passing them to tool handlers. This forces a specific PHP representation on consumers instead of preserving the original JSON types.

Describe the solution you'd like

Pass validated arguments to tool handlers without implicit type conversion:

  • JSON objects → stdClass
  • JSON arrays → array
  • Scalar values → their corresponding PHP types

This should apply recursively to nested structures.

For consumers preferring associative arrays, the SDK could provide an optional, documented recursive stdClass-to-array converter. Its use should be explicitly controlled by the consumer.

Describe alternatives you've considered

A configurable automatic conversion to associative arrays would preserve existing behavior, but introduce application-specific conversion logic and additional maintenance overhead into the SDK's argument-handling pipeline.

Existing Composer packages also provide object-to-array conversion, so consumers could handle this independently without additional SDK functionality.

Additional context

Related to #586, which addresses the loss of JSON type information during decoding and its impact on schema validation.

This request concerns the subsequent delivery of validated values to tool handlers.

The change would be breaking for consumers expecting associative arrays, but could be introduced before the SDK reaches 1.0. Preserving the current interface merely for convenience or backward compatibility would be an unfortunate design decision, as it would perpetuate unnecessary coupling to a specific PHP representation instead of establishing a clean, type-preserving API.

Lingua principale
PHP
Stelle
1.6k
Fork
180
Merge medio
2g 16h
PR unite (30g)
36

Preparare l'ambiente

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 modelcontextprotocol/php-sdk

Tutte le issue di modelcontextprotocol/php-sdk

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.