Skip to main content
Glama

List resources

list_resources
Read-only

A project's RESOURCES for its calendar: rooms and units of equipment — each unit its own row (four lights of one model are four). Each has 'kind' (room, equipment), 'status' (available, repair — a resource under repair is not given to an event), 'x'/'y' (where it stands on the plan, millimetres), 'bufferBefore'/'bufferAfter' (minutes for setting up and clearing, counted as busy) and 'externalId'. Any member may read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: status semantics (a resource under repair is not given to an event), buffer minutes counted as busy, coordinate units in millimetres, and the read-permission rule. It stops short of return shape or pagination details.

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?

One front-loaded sentence carries the definition, and the parenthetical field explanations are dense but each one conveys semantics rather than repetition. It is slightly run-on but wastes little.

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?

With no output schema, describing the fields an agent will see (kind, status, x/y, buffers, externalId) is the right compensation, and the auth note is included. Only return shape and ordering are unstated, which is minor for a one-parameter read 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?

There is a single parameter, `project`, and its schema description already covers the key format at 100% coverage. The description never mentions the parameter, so it adds nothing beyond the schema and the baseline 3 applies.

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?

The description names the resource being listed and defines it concretely: rooms and equipment units for a project calendar, with each unit as its own row. It is clear enough to separate from event- or person-oriented siblings, though it never opens with an explicit verb like "Lists" and does not name an alternative tool.

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 only implied: the agent can infer this is the tool for fetching room/equipment definitions, and "Any member may read" sets the permission context. There is no explicit when-to-use versus when-to-use-something-else guidance and no stated exclusions.

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