Skip to main content
Glama

Get a project

get_project
Read-onlyIdempotent

Use this when you need one project's details in a single call: its public page URL, pipeline stages, capture forms (with the identity each one collects) and headline audience numbers. Use it after list_projects and before a write. Not for arrival rates over time (use get_audience_stats) or for finding a project's handle (use list_projects).

Each form lists its fields (key, label, type, required) and requires_verification, which is the form's "Ask people to verify their email" switch. Use them to tell the founder what a person sees on the signup form and what they receive afterward: when it is on, a new signup is sent an email asking them to verify their address, and when it is off they are not.

The forms list tells you which frm_… handle to pass to capture_signup and what identity that form expects: a form that collects a phone number will not accept an email. The stages list gives the exact stage keys update_contact_stage accepts; the founder renames these, so never guess one.

Counts here are precomputed aggregates, not a scan, so this is cheap even on a million-contact audience.

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

Input Schema

NameRequiredDescriptionDefault
projectYesThe project handle, like `prj_…`. From `list_projects`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds real behavioral context on top: counts are precomputed aggregates rather than a scan, so cost is flat even on a million-contact audience. It also explains the semantics of `requires_verification` and warns that stage keys are founder-renamed and must not be guessed.

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?

Purpose and routing come first, then the return-content detail, which is the right order. The middle paragraphs on forms and stages are dense with useful guidance, though the email-verification explanation runs slightly long for what it conveys.

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

Completeness5/5

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

No output schema exists, so the description carries the return-shape burden and does so: it enumerates the returned fields and explains the nested `fields` and `requires_verification` structure of forms. For a single-parameter read tool, nothing an agent needs to call it correctly 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?

Schema coverage is 100% and the schema already says the parameter is a `prj_…` handle from `list_projects`, which the description only restates. No extra detail on the handle format or failure modes is added beyond what the schema provides, so the baseline of 3 applies.

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?

Names a specific verb and resource (get one project's details) and enumerates what comes back: public page URL, pipeline stages, capture forms, headline audience numbers. It explicitly disambiguates from get_audience_stats and list_projects, so an agent can separate it from siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete sequencing guidance ('after `list_projects` and before a write') plus explicit exclusions with the correct alternatives named for each (arrival rates → get_audience_stats, handles → list_projects). Both when-to-use and when-not-to-use are covered.

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.