yuqi1129 opened a new issue, #13122:
URL: https://github.com/apache/gravitino/issues/13122
### Version
main branch
### Describe what's wrong
The MCP statistics tools `list_statistics_for_metadata` and
`list_statistics_for_partition` require `metadata_fullname`, while the tag and
policy tools use `metadata_full_name` for the same identifier. A caller using
the spelling shared by the other tools fails argument validation before any
REST request is made.
The public tool schemas should consistently advertise `metadata_full_name`.
Existing callers using `metadata_fullname` should remain supported.
### Error message and/or stacktrace
```text
2 validation errors for call[list_statistics_for_metadata]
metadata_fullname
Missing required argument
metadata_full_name
Unexpected keyword argument
```
### How to reproduce
1. Inspect `tools/list`: statistics tools require `metadata_fullname`, while
tag and policy tools require `metadata_full_name`.
2. Call `list_statistics_for_metadata` with `metadata_type: table` and
`metadata_full_name: catalog.schema.table`.
3. Observe the validation error. Using `metadata_fullname` succeeds.
4. Repeat with `list_statistics_for_partition`, supplying
`from_partition_name` and `to_partition_name`; the same inconsistency occurs.
### Additional context
Reproduced through in-process MCP calls on main at
`441e590b98dba14bbd176a0660ce88cd39368476`, using mocked backend operations.
This report covers the metadata full-name spelling; tag/policy association list
argument naming is a separate consistency concern.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
