Skip to main content
Glama

Get institution detail

get_institution
Read-onlyIdempotent

Institution or group profile: identifiers, members, funded projects and credited items, with citation links.

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

Input Schema

NameRequiredDescriptionDefault
idNoOmeka id or typed id organisation:1224
nameNoInstitution or group name, or an acronym

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed4 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    }
      +  ],
      +  "description": "Omeka id or typed id organisation:1224"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Institution name"New value: +"Institution or group name, or an acronym"
    • addedInput schema / properties / name / maxLength
      Added value: +1000
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine content disclosure — members, funded projects, credited items, citation links — which tells the agent what payload to expect. However, it never addresses the fact that both parameters are optional, leaving the no-argument behavior and result shape unexplained.

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?

A single compact clause with the resource front-loaded and zero filler. It reads as a label rather than a sentence, which slightly weakens scannability but costs no tokens.

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 two-optional-parameter read tool with full schema coverage and no output schema, the description covers the returned content well. The remaining gap is behavioral: with zero required parameters, the definition should clarify selector requirements (id vs name vs neither) for an agent to invoke it confidently.

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 description coverage is 100%, and the schema itself supplies the typed-id example ('organisation:1224') and the acronym nuance. The description adds no selector semantics beyond that — notably it does not say whether id or name takes precedence or that either alone suffices.

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?

Names the resource (institution or group profile) and enumerates what it contains: identifiers, members, funded projects, credited items and citation links. It is clearly the singular detail counterpart to list_institutions and distinct from get_person/get_project, though the verb is implicit (a noun-phrase fragment rather than 'Retrieve...').

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 when-to-use guidance and no named alternative. An agent must infer that this is the detail lookup versus list_institutions (browse) or resolve_entity, and nothing states whether calling it with no arguments is valid or what happens then.

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.