Skip to main content
Glama

List fields

list_fields
Read-only

The catalogue of the facts: key, entity (parcel or unit), group, type, unit, label and source of each field.

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

Input Schema

NameRequiredDescriptionDefault
groupNo
entityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 safety and locality are covered and the description need not repeat them. In exchange, the description contributes useful behavioral context by revealing the shape and scope of the returned catalogue (the per-field attributes), which matters because no output schema exists. It stops short of saying whether the catalogue is static, whether results are paginated, or how large the list typically is.

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?

A single short sentence with no wasted clauses, but it is front-loaded with a metaphor ("the catalogue of the facts") instead of the operative information, and the inline list of attributes reads as a run-on. It is compact without being well structured.

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?

With no output schema, the description's enumeration of returned attributes is genuinely needed and is the strongest part of the definition. However, for a tool with a filterable group parameter and a sibling search_fields, the absence of any filtering semantics or selection guidance leaves real gaps.

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?

Schema description coverage is 0% on two parameters, so the description must carry the burden and only partly does. It clarifies the meaning of entity by echoing the enum values already present in the schema, but says nothing about the group filter — whether it narrows the catalogue to a field group, what group values exist, or whether omitting it returns everything.

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 frames the tool as "the catalogue of the facts" and enumerates the attributes each entry carries (key, entity, group, type, unit, label, source), which implies a read of field definitions rather than data. But it never states a verb or the resource being listed (fields/field catalogue), so the reader must infer the tool returns field metadata from the name and the attribute list.

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 when-to-use guidance at all: no statement of what this catalogue is for, no distinction from search_fields, and no indication of when to call it before other fact-retrieval tools. The only hint is the parenthetical "(parcel or unit)", which describes a value domain rather than a usage condition.

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