Skip to main content
Glama

Organisations Index

organisations_index

Retrieve a paginated list of organisations, using page number, page limit, and query parameters to sort, filter, search, and select fields.

Instructions

Get collection of organisations. GET /organisations

page_number/page_limit map to page[number]/page[limit]; query passes extra query parameters (sort, filter, q, fields[organisations]) through verbatim.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; the embedded "GET" makes the read-only nature clear and it reveals the JSON:API pagination mapping and that query supports sort/filter/q/fields. It omits auth requirements, rate limits, default page sizes, and any return-format description.

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?

Two short sentences that front-load the purpose before the parameter notes, with no filler. The backtick-heavy formatting is compact and readable.

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 simple three-optional-parameter list tool with no annotations and no output schema, the description covers purpose, endpoint, pagination mapping, and filter passthrough. It still leaves gaps around pagination defaults, response shape, and whether filtering is required for a useful result.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: page_number/page_limit are explained as mapping to page[number]/page[limit], and query is explained as verbatim passthrough of parameters with concrete examples (sort, filter, q, fields[organisations]). This is real added meaning beyond the bare schema, though it does not state accepted value formats for the integer params.

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?

"Get collection of organisations" states a specific verb (get) and resource (organisations) and the endpoint GET /organisations reinforces that it is a list operation. It does not explicitly distinguish itself from organisations_show (single-record retrieval), so an agent must infer the difference from the word "collection".

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 statement of when to use this versus organisations_show or the statistics/events siblings, and no prerequisites or exclusions are given. Only the implicit signal of "collection" hints this is the list endpoint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.