Skip to main content
Glama

Get one project record

get_project
Read-onlyIdempotent

One project. representation="standard" is the default (headline, summary, parties, size, without minutes). representation="full" includes the filing text and document ids. Does not use credits from the Find Contact Info allowance. Each new or changed record counts toward 100,000 export records a month on County, State, and National plans. An unchanged record already delivered does not. On API Only and the trial, costs 1 credit the first time this account receives the record. Email, phone, and personal LinkedIn come only from create_enrichment, which searches for them and may find none. A thin record is an early agenda item. get_credit_balance returns the remaining balance.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYes
representationNoDefaults to standard (product page without minutes). Use full only for one filing; never in a loop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description goes well beyond them: it discloses the credit model (excluded from the Find Contact Info allowance; 1 credit on API Only/trial for first receipt), the 100,000/month export-record quota with the "unchanged record already delivered does not count" nuance, and which fields are absent without enrichment. This is exactly the cost/latency-style context the annotations cannot convey.

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?

The billing and quota material is dense but earns its place; however, the opening is a bare fragment and "A thin record is an early agenda item." is cryptic filler that spends space without conveying actionable meaning. Billing rules, data-shape rules, and cross-tool pointers run together without structure, making the important default (standard representation) easy to miss.

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?

With no output schema, the description takes on the return-value burden and largely meets it by enumerating what standard and full include. Costs and quota accounting are covered. Gaps remain: the compact representation, behavior on a nonexistent projectId, and what a "project" actually is (permit/filing record) are unaddressed.

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 50%. The description explains what standard returns (headline, summary, parties, size, without minutes) and that full adds filing text and document ids, which meaningfully extends the schema's enum note. But the "compact" enum value is never described in either the schema or the description, and projectId carries no description anywhere despite being required.

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?

"One project." is a fragment, not a verb+resource statement; the retrieval semantics only become inferable from the later discussion of what "representation" includes. A reader can guess this fetches a single project record (as opposed to the sibling get_projects), but the description never says "retrieve" or "returns" the record, and it never contrasts itself with the list tool.

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?

It gives real routing guidance: contact fields (email, phone, personal LinkedIn) come only from create_enrichment and may not exist, and get_credit_balance is named for checking the remaining balance. It also signals representation choice (standard is the default; full adds filing text). It lacks any explicit when-to-use-this-vs-get_projects or get_document guidance, so it stops short of a 5.

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