Skip to main content
Glama

Look at a research project

get_project
Read-only

Check a research project's status by project ID, including its state, required input, scoping plan, last agent message, deliveries, credits used, and allowed next actions.

Instructions

Where a research project stands: its state (queued, working, input_required, completed, failed, cancelled, rejected), what it needs from the user, the scoping questions or the plan, the agents' last message, deliveries, credits used, and the actions allowed now. Free.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesThe project id start_project returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that by disclosing the full state vocabulary (queued, working, input_required, completed, failed, cancelled, rejected) and the fact that the call is free, which matters for polling frequency. It still doesn't say whether the call is idempotent, how large the payload is, or how to interpret input_required responses.

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?

One front-loaded sentence that puts the purpose first and the field list after, with zero filler and no repetition. The dense comma-separated enumeration is slightly hard to scan but every item earns its place by telling the agent what it will receive.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly via the field enumeration and state list. Combined with the readOnlyHint annotation and full parameter coverage, an agent has enough to call it correctly; only guidance on how to react to specific states is missing.

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?

There is a single parameter with 100% schema coverage, and the schema already explains it is 'The project id start_project returned'. The description adds nothing further about the id (format, where to find it, reuse across calls), 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?

States a specific resource (research project) and enumerates exactly what is returned: state, what it needs from the user, scoping questions/plan, agents' last message, deliveries, credits used, and allowed actions. That is far more concrete than a tautology. It stops short of naming a sibling, so an agent must infer on its own that this is the read counterpart to act_on_project or wait_for_project.

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

Usage Guidelines3/5

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

Usage is only implied: the enumeration of state values and 'the actions allowed now' signals this is a status/polling call, but the description never says when to call it versus wait_for_project (long-polling) or act_on_project (taking an action). No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.