Skip to main content
Glama

Jonas Splinter (jsplinter.nl)

Get project details

get_project
Read-onlyIdempotent

Full details of one project: what it is, key figures with the month they were taken, what it offers, important pages, social channels, milestones, the technology where published, and the newest updates about it. Keys come from list_projects.

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

Input Schema

NameRequiredDescriptionDefault
keyYesProject key as returned by list_projects, one of: blockspot, voucheralarm, automateandtweak, games. Example: "blockspot".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 fully covered. The description adds value by disclosing the shape of the returned content, which matters because there is no output schema, but it says nothing about size, pagination, or error behavior for an invalid key.

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 that leads with the resource and then enumerates the payload. The field list is long but each item conveys what the agent will receive; minor density is acceptable given the absence of an output schema.

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

Completeness4/5

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

For a one-parameter read tool with full annotation coverage, the description supplies the missing piece: what the response contains, since no output schema exists. Only the invalid-key failure behavior is left unaddressed, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already lists the allowed keys with an example. The description reinforces this by stating the provenance of the key ("Keys come from list_projects"), which helps an agent know where to obtain a valid value rather than guessing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Full details of one project") and enumerates the content returned: key figures with their month, offerings, pages, social channels, milestones, technology, and newest updates. This clearly distinguishes it from list_projects, which only supplies keys.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence "Keys come from list_projects" establishes the prerequisite and the natural workflow ordering. It does not explicitly state when not to use it (e.g., use list_projects for a summary), but the context is clear enough for an agent to sequence the calls.

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.

Resources