Skip to main content
Glama

get_institution

Get an institution's detail, its country, its grading override and its resolved grading scale.

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
slugNoInstitution slug (or name, as a fallback)
institution_idNoinstitutions id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read, but nothing is said about what happens when both parameters are omitted (required is empty), what error surfaces for an unknown slug, or whether lookups are cached or rate-limited — meaningful gaps for a tool with zero annotation coverage.

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 front-loaded sentence with no filler. The repeated 'its ... its ... its' construction is slightly awkward but does efficiently enumerate the returned fields rather than padding the text.

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 does useful work by naming the four components of the response. However, it remains thin for a lookup tool whose parameters are both optional: it never explains the no-argument case, identifier precedence, or failure modes, leaving real gaps.

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%, so both parameters are already documented, and the fallback behavior of slug is stated in the schema. The description adds nothing about slug-vs-institution_id precedence or which one wins if both are passed, so baseline 3 is appropriate.

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 ('Get') and resource ('an institution') and enumerates the payload: detail, country, grading override, resolved grading scale. That distinguishes it reasonably well from get_country_guide or resolve_grading_scale, though the description never explicitly contrasts itself with those siblings.

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 and no mention of alternatives such as get_country_guide or resolve_grading_scale, which overlap with the country and grading-scale portions of the response. It also gives no guidance on choosing between the two optional parameters or what happens when neither is supplied.

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.