Skip to main content
Glama

get_project

Retrieves a project's datasets and model fits by project ID, helping you inspect associated conjoint analysis data and results.

Instructions

A project with its datasets and fits.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no read-only assurance, no error behavior for an unknown project_id, no indication of whether nested datasets and fits are always included or how large the response can get. The only behavioral hint is the word 'with', implying nested expansion.

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

Conciseness3/5

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

It is only five words with no filler, but that brevity reflects under-specification rather than disciplined editing; it is a noun fragment, not a front-loaded statement of action and result.

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

Completeness2/5

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

There is no output schema and no annotations, and the tool returns a nested object, so the description should at minimum describe the shape or key fields of the project, its datasets, and its fits. It does not, leaving the agent unable to predict the response.

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

Parameters2/5

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

Schema coverage is 0% for the single required project_id, so the schema says nothing about format or provenance. The description never mentions the parameter, leaving the agent to guess whether it is a UUID, slug, or numeric ID, or where to obtain it.

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

Purpose3/5

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

The fragment 'A project with its datasets and fits' does add one fact beyond the name: the returned object bundles datasets and fits, which hints at a nested retrieval rather than a bare record. However, there is no verb and no scope statement, so an agent must infer that this fetches a single existing project by ID rather than listing or creating one.

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 at all, and no mention of the obvious alternative list_projects or of any prerequisite such as needing a valid project_id from a prior listing. The agent gets no signal about when this tool is the right choice versus its siblings.

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