Skip to main content
Glama

github_users_delete_attestations_by_id

Delete a specific attestation for a GitHub user by providing the username and attestation ID.

Instructions

Delete attestations by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesusername
attestation_idYesattestation_id
Behavior2/5

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

No annotations provided, so description carries full burden. Only states it deletes, but lacks details on consequences, success/failure behavior, permissions, or reversibility. Minimal behavioral disclosure.

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?

Extremely concise, one phrase with no unnecessary words. Front-loaded and efficient, but could benefit from a bit more context.

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?

Given no annotations and no output schema, the description is too minimal. It doesn't explain the deletion's scope, side effects, or how to find the attestation_id. Incomplete for a deletion tool.

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% but schema descriptions are just parameter names. Description adds context that attestation_id is the ID. However, it doesn't clarify what username refers to or the format of attestation_id. Partially compensates for poor schema descriptions.

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?

Description 'Delete attestations by ID' clearly states the verb (Delete), resource (attestations), and identifier (by ID). It distinguishes from sibling tools like 'delete_attestations_bulk' and 'delete_attestations_by_subject_digest'.

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?

No guidance on when to use this tool versus alternatives. Does not mention that it deletes a single attestation by its ID, or provide context about prerequisites or how to obtain the ID.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/github-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server