Skip to main content
Glama

saagarpatel.dev Portfolio

Get repo profile

get_repo_profile
Read-only

Return one public-safe repo answering profile by repo_id, including purpose, safe commands, agent surfaces, proof refs, freshness, exclusions, limitations, and integrity metadata.

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": {
      "repoId": "<repoId>"
    },
    "name": "get_repo_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoIdYesRepo profile id, e.g. "githubrepoauditor"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real context beyond that by promising 'public-safe' content, 'exclusions, limitations, and integrity metadata', and 'freshness' — signaling that stale or partial data may be surfaced. It omits not-found/error behavior, which for a keyed single-record lookup is the main remaining gap.

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 naming the action, key, and returned payload with no filler. The trailing field list is dense but each item (safe commands, exclusions, limitations, integrity metadata) conveys distinct content, so little is wasted.

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 usefully enumerates what the response contains, which is the information an agent needs to decide to call it. The only shortfall is the absence of behavior for a missing or non-public repo_id.

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 required parameter with 100% schema coverage and an inline example ('githubrepoauditor'), so the schema already does the work. The description only restates that the lookup is by repo_id and adds no format, casing, or validity rules.

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 states a specific verb and resource ('Return one public-safe repo answering profile by repo_id') and enumerates the fields returned, so the purpose is unambiguous. It distinguishes itself from a listing operation only implicitly via 'one', never naming list_repo_profiles or get_profile.

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 implied: single-item retrieval keyed by id, which suggests list_repo_profiles is the alternative for enumerating profiles. However, no explicit when-to-use guidance, no note on which sibling to choose for non-repo profiles (e.g. get_profile), and no mention of what to do when the id is unknown.

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.