Skip to main content
Glama

Search fields

search_fields
Read-only

The filter fields of one search entity: code, label, type, operators, facet, sortable, and the token scope a field needs.

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_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityNounit (default), parcel, building or listing (agency-website adverts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by naming the exact attributes present in each returned field, which tells the agent what it can learn from the call. It does not state whether results are static metadata or configurable per entity, nor anything about shape or size beyond the attribute list.

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

Conciseness4/5

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

A single well-formed sentence with the resource front-loaded and no filler. The closing phrase 'the token scope a field needs' is somewhat cryptic, but nothing is wasted.

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

Completeness3/5

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

For a one-optional-parameter read tool with annotations and no output schema, the description covers what is returned, which is the main gap an agent would otherwise face. It still leaves the operation type and its relationship to the 'search' tool unstated, so it is adequate rather than complete.

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

Parameters3/5

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

Schema coverage is 100% and the single 'entity' parameter is fully described with its enum in the schema. The phrase 'one search entity' echoes the parameter but adds no meaning beyond it, so the baseline of 3 applies.

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 identifies the resource ('the filter fields of one search entity') and enumerates the attributes returned (code, label, type, operators, facet, sortable, token scope). However, it is a bare noun phrase with no verb, so an agent must infer that this is a lookup/list operation, and nothing distinguishes it from the sibling 'list_fields', which sounds nearly identical.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as 'search' or 'list_fields'. The intended workflow (discovering filterable fields before calling search) is only inferable from the noun 'filter fields'.

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