Skip to main content
Glama

search_targets

Read-only

Search the targets: quantities with a direction and a record history, where AI work moved a bound or produced a better object rather than settling a statement.

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": "search_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoText to match in id, name, collection or tags
standingNo
collectionNo
checked_onlyNoOnly targets whose object was rebuilt here
held_by_machineNoOnly where the leading record is a machine's

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

The readOnlyHint=true annotation is consistent with the 'Search' framing, so there is no contradiction. Beyond that, the description adds little behavioral context: it does not explain result ordering, how the default limit applies, what happens with an empty query, or what 'record history' means operationally.

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?

The description is a single front-loaded sentence and avoids repetition or filler. However, the trailing definition is elliptical and hard to parse, adding length without adding actionable clarity for the agent.

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?

For a tool with six optional filters, no output schema, and only a readOnly annotation, the description is under-informative. It does not explain how filters combine, what the search returns, or what distinguishes the enumerated standing values, leaving the agent unable to construct queries confidently.

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

Parameters2/5

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

The tool has six parameters and only 50% schema description coverage, so the description should compensate for gaps. It does not explain limit, query, standing, collection, checked_only, or held_by_machine; the phrase 'record history' is the only faint link to 'standing', and it is not enough to clarify filter semantics.

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?

The description starts with a clear verb and resource, 'Search the targets', and attempts to define what a target is. However, the definition ('quantities with a direction and a record history, where AI work moved a bound or produced a better object rather than settling a statement') is dense domain jargon that an agent may not decode, and the contrast with 'settling a statement' only obliquely distinguishes this from sibling searches.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as search_statements, search_formalisations, or get_target. The phrase 'rather than settling a statement' hints at a distinction, but it does not tell the agent when this search is appropriate or when another tool should be preferred.

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