Skip to main content
Glama

Get research section detail

get_research_section
Read-onlyIdempotent

One research section's description, team and projects, each with its research-item count.

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_research_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSection Omeka id or typed id section:<id> from list_research_sections; not with name
nameNoSection name, e.g. 'Arts & Aesthetics' ('and' for '&' works)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Section Omeka id or typed id section:218"New value: +"Section Omeka id or typed id section:<id> from list_research_sections; not with name"
    • changedInput schema / properties / name / description
      Previous value: -"Section name, e.g. 'Arts & Aesthetics'"New value: +"Section name, e.g. 'Arts & Aesthetics' ('and' for '&' works)"
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    }
      +  ],
      +  "description": "Section Omeka id or typed id section:218"
      +}
    • addedInput schema / properties / name / maxLength
      Added value: +1000
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  4. 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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the return shape (description, team, projects, per-project research-item counts), which matters since there is no output schema. It says nothing about lookup behavior or what happens when neither id nor name resolves.

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 no wasted words, and the return payload is front-loaded. The telegraphic noun-phrase form is efficient but reads as an incomplete sentence.

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 the necessary minimum by naming the returned fields. However, it omits how id versus name are resolved, what happens on ambiguity or no match, and whether related projects are expanded or truncated.

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%, with both id and name fully documented including the 'section:<id>' typed-id format and the 'not with name' exclusivity rule. The description adds no parameter meaning beyond that, so 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?

Identifies a specific resource (one research section) and enumerates the payload it returns: description, team, projects, and research-item counts. This clearly separates it from list_research_sections and get_research_item. It is phrased as a noun fragment with no verb, which slightly weakens the statement of action.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as list_research_sections or get_research_item. The only workflow hint ('from list_research_sections') appears in the schema, not the description.

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.