Get all keys from a JSON object.
| Name | Required | Description | Default |
|---|---|---|---|
| json_string | Yes | JSON object string |
| Name | Required | Description | Default |
|---|---|---|---|
| keys | No | ||
| type | No | ||
| error | No | ||
| valid | No | ||
| key_count | No | ||
| all_keys_nested | No | ||
| total_nested_keys | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It omits error handling (e.g., invalid JSON), key order, or behavior for non-object inputs. Only states basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence with no wasted words. Appropriate length for a simple utility tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is simple with one parameter and output schema exists. However, missing details about error behavior and assumptions (e.g., input must be a valid JSON object) leaves gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with parameter description 'JSON object string'. Tool description adds no extra meaning beyond repeating 'JSON object'. Baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool extracts all keys from a JSON object using a specific verb and resource. No sibling tool directly overlaps, so it distinguishes well.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Given many sibling tools, users receive no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes, such as multiple random generators (random_integer, random_number), duplicate hashing functions (hash_md5, md5_checksum), and near-identical tools (compare, compare_2, compare_decimals). The sheer number of tools and lack of clear boundaries make it difficult for an agent to differentiate.
Naming is highly inconsistent. There are duplicate tools with different names (camel_case vs to_camel_case, slug vs slugify), arbitrary suffixes like '_2', and mixing of patterns (e.g., generate_password vs password_entropy). No clear convention is followed.
With 572 tools, the server is massively overpopulated for any coherent purpose. It includes trivial endpoints (true_endpoint, null, hello_world) and numerous duplicates, far exceeding a well-scoped utility set.
While the server covers many domains (math, strings, dates, colors, etc.), the presence of duplicate and trivial tools indicates a lack of thoughtful curation. There are gaps in basic operations (e.g., no dedicated file or network tools), and many tools are redundant.
