Skip to main content
Glama

Organisations Show

organisations_show

Retrieve details for a specific organisation by ID and pass field filters through the query parameter to support API management and reporting.

Instructions

Get details of an organisation. GET /organisations/{organisationId}

query keys (fields[organisations]) pass through verbatim.

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": {
      "organisation_id": "<organisation_id>"
    },
    "name": "organisations_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses little beyond the HTTP verb. It says nothing about permissions, 404 behavior for unknown IDs, or what 'details' comprises; the only behavioral note is that query keys pass through verbatim.

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?

Two short sentences, front-loaded with purpose, so there is little waste. However, the second sentence is cryptic shorthand that costs more parsing effort than it earns in clarity.

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

Completeness2/5

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

No annotations and no output schema means the description is the only place to convey behavior, and it leaves the return shape, error cases, and parameter meanings unaddressed. An agent can construct the call but cannot predict what comes back.

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%, so the description must explain both parameters, yet it never defines organisation_id and describes query only obliquely as 'fields[organisations] pass through verbatim'. That phrasing hints at a sparse-fieldset syntax but gives no example or naming rules.

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 ('Get details of an organisation') and pins it to a single-resource endpoint, which implicitly separates it from the plural organisations_index sibling. It stops short of explicitly contrasting with that sibling by name.

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 over organisations_index or the statistics/events siblings. Single-record retrieval is weakly implied by the path template, but the agent gets no routing guidance or prerequisites.

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