Skip to main content
Glama

Find attributes

find_attributes
Read-onlyIdempotent

Search the attribute catalog by keyword or category. Returns the columns to use in criteria and requirements, and whether each is locked on the user's plan.

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

Input Schema

NameRequiredDescriptionDefault
groupNocategory path prefix, e.g. Affordability or Mobility.Commute
queryNowords to match in a label, description or category, e.g. commute time

Output Schema

NameRequiredDescriptionDefault
moreNo
attributesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, closed-world lookup, so the bar is low. The description still adds a genuinely new behavioral fact: results are gated by the user's plan, which explains why some attributes come back locked — context an agent needs in order to interpret 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.

Conciseness5/5

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

Two short sentences, purpose first and return semantics second, with no filler. Every clause carries information and the response shape is front-loaded.

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

Completeness4/5

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

Both parameters are optional and an output schema exists, so the description need not restate return fields. The one remaining gap is behavior with no arguments — whether an empty call lists the whole catalog — which matters for a zero-required-parameter tool.

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 both parameters already carry descriptions with examples, so the description adds essentially nothing new about 'group' or 'query'. Baseline 3 applies since the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb and resource ('Search the attribute catalog') and goes on to say what the results are used for ('columns to use in criteria and requirements'). It is clearly not a places/geocoding tool, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the return description: reach for this when you need the attribute columns that criteria and requirements reference. There is no explicit when-not guidance or named alternative, so the agent must infer the boundaries itself.

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