Skip to main content
Glama

Get project detail

get_project
Read-onlyIdempotent

Project description, team, sections, funders, item counts by type, top subjects and ten sample research items, with citation links.

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": {
      "id": "<id>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProject Omeka id (e.g. 37700) or typed id project:37700
include_similarNoAdd up to 5 similar records, each explained

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_similar
      Added value: +{
      +  "description": "Add up to 5 similar records, each explained",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "maxLength": 256,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / id / description
      Previous value: -"Project Omeka o:id, e.g. 37700"New value: +"Project Omeka id (e.g. 37700) or typed id project:37700"
    • removedInput schema / properties / id / type
      Removed value: -[
      -  "string",
      -  "number"
      -]
  3. First observed

TDQS

A3.5/5.0
Behavior4/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 real value beyond them by disclosing the shape of what comes back (ten sample items rather than all, citation links included) — important because there is no output schema. It omits any mention of what happens for a missing id or a very large project.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with zero filler; every listed item is part of the return contract, and the payload enumeration is front-loaded. No repetition of the title or name.

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 carries the burden of explaining return values and does so reasonably well for the main payload. It leaves gaps: nothing about the include_similar output, pagination/truncation of the ten samples, or error behavior, which matter for a detail-fetch tool.

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 coverage is 100%, with both parameters documented in-schema, including the id formats and the include_similar behavior. The description adds no parameter meaning at all — it never mentions include_similar or that similar records get explanations. Baseline 3 applies since the schema carries the load.

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?

The description names the resource (a project) and enumerates its payload precisely — description, team, sections, funders, item counts, top subjects, ten sample items, citation links — so an agent knows this returns a rich project detail record rather than a list or a narrow sub-resource. It stops short of an explicit verb ('retrieve project by id') and never contrasts itself with near-siblings like get_collection_overview or get_research_item, so it is clear but not differentiating.

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 or when-not-to-use guidance: nothing says to call this after a search result, instead of get_research_item, or when a project id is already known. The agent must infer usage purely from the tool name and the enumerated payload.

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.