Skip to main content
Glama

Little Works

get_anything_capabilities

How to get anything: catalog hit → buy/hire; miss → request_source (source / find / build).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_anything_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, no output schema, and the description says nothing about whether this is a read-only lookup, what it returns (a capability list? a hit/miss signal?), or any side effects. Since nothing structured covers the behavior, the description carries the full burden and does not meet it. An agent cannot tell what a "hit" even looks like in the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is extremely short and front-loads the routing rule, which is good. However, the arrow notation and the unexplained parenthetical "(source / find / build)" are cryptic shorthand that cost clarity; brevity here shades into under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero params, no annotations, and no output schema, the description is the only source of information about this tool, yet it never explains the return value or what distinguishes a hit from a miss. For a routing/catalog tool whose whole value is deciding the next call, that gap is significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description neither adds nor omits anything meaningful here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"How to get anything" gestures at a capability/catalog lookup but never says what the tool actually returns or what operation it performs. The "catalog hit → buy/hire; miss → request_source" phrasing reads as routing advice rather than a statement of purpose. It does implicitly distinguish itself from request_source by casting itself as the first stop, but the verb+resource pair is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition gives an explicit conditional routing rule: a catalog hit means go to buy/hire, a miss means go to request_source, and it names the sibling to use in that case. What it lacks is a direct statement of when to invoke this tool itself (presumably before any buy/hire or request_source call), so the guidance is inferential rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources