Skip to main content
Glama

Vercel OSS Registry

Get Vercel OSS project details

get_project
Read-onlyIdempotent

Full catalog record(s) for one or more project ids (owner/repo) returned by search_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": {
      "ids": "<ids>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesowner/repo ids, case-insensitive; a full GitHub URL also works

Output Schema

NameRequiredDescriptionDefault
notFoundYes
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 by structured data. The description adds that the tool is batch-oriented ('one or more') and returns complete rather than partial records. It does not disclose the practical cap of 10 ids, behavior on unknown ids, or whether missing ids are silently dropped.

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

Conciseness5/5

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

A single tightly-written sentence with no filler, front-loading the return payload and then the input provenance. Nothing in it is redundant with the schema at the cost of clarity.

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 lookup tool with a full output schema and complete annotations, the description covers purpose, input provenance and batch capability. The remaining gaps (partial-miss behavior, the 10-id cap) are minor and partly encoded in the schema.

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 description coverage is 100%, so the schema already explains the owner/repo format, case-insensitivity, URL acceptance and the 1-10 item bounds. The description adds only the provenance hint that ids should come from search_projects, which is a modest increment over the schema. Baseline 3 is appropriate.

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?

The description names a specific resource ('full catalog record(s)') and a specific selector ('one or more project ids'), and the word 'full' implicitly contrasts with the lighter results from search_projects. It stops just short of an explicit differentiation statement, but an agent can still tell it apart from search_projects.

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?

'returned by search_projects' establishes the prerequisite provenance of the ids, which is useful implied guidance. There is no explicit when-to-use/when-not guidance, no mention that the call fails or skips unknown ids, and no stated alternative when ids are not already known.

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.