Skip to main content
Glama

Attify

Verification program status

get_program_status
Read-onlyIdempotent

Your verification programs, as a vendor: phase, public status (Claim confirmed · within 5.0 points, Claim not confirmed, Lapsed or Revoked, or private), the one next step, each publishing minimum met or missing in your own numbers, what the latest score still waits for before it publishes, the claimed unit as Attify recorded it, and your customers' connection and consent. It states where the program stands; it never advises how to raise a score. Needs sign-in to Attify; reads only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_program_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
programNoOne program: its id, profile slug or product name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, but the description adds meaningful context beyond them: sign-in to Attify is required, it only reads, and it explicitly does not advise on improving scores. It also discloses the returned status categories and data dimensions, which is valuable because there is no output schema.

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?

The description is front-loaded with purpose and then efficiently enumerates the returned fields, which is appropriate without an output schema. It is somewhat dense as a single long sentence, but each clause contributes useful information about scope, output, or constraints.

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 read-only, single-parameter status tool with no output schema, the description is largely complete: it covers purpose, the data returned, public status values, access requirements, and the advisory limitation. It could be improved by clarifying the no-parameter behavior and any pagination or listing behavior, but the core context is present.

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 explains that 'program' can be an id, profile slug, or product name. The description does not add parameter-specific meaning beyond the schema, and its plural phrasing ('Your verification programs') does not clarify whether omitting the optional parameter returns all programs or only the default.

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 clearly identifies the resource as a vendor's verification program status and enumerates the specific data returned: phase, public status, next step, publishing minimums, score blockers, claimed unit, and customer connection/consent. It also distinguishes itself from advisory tools by stating it never advises how to raise a score, though it does not explicitly name sibling tools.

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 by 'Your verification programs, as a vendor' and 'Needs sign-in to Attify; reads only,' which gives audience and access context. However, it does not explicitly say when to use this tool versus alternatives such as get_verdict or get_monthly_verdict, nor does it state what happens if the optional program parameter is omitted.

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