Skip to main content
Glama

FindMyBids

Registration guide

get_walkthrough
Read-onlyIdempotent

Step-by-step registration guide. portal: a state code or name ("PA", "Ohio"), "sam" for SAM.gov, or "us-sba-certifications" for SBA set-aside certifications. Also returns bid_forms: the standard affidavits, certifications, bonds and diversity forms bidders are commonly asked for there, with links to the official blank forms.

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": {
      "portal": "<portal>"
    },
    "name": "get_walkthrough"
  }
}

Input Schema

NameRequiredDescriptionDefault
portalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety behavior is covered. The description adds useful return behavior beyond annotations by explaining that bid_forms include affidavits, certifications, bonds and diversity forms with links to official blank forms, though it does not describe the full guide output shape.

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?

The description is front-loaded with the tool's purpose, followed by parameter values and return details. Every sentence adds useful information and there is no redundant wording.

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 read-only tool with no output schema, the description gives sufficient context about accepted portal values and an important returned field. It could be slightly more complete by describing the overall guide return structure, but the core information needed to call it is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It does this well: it explains that portal accepts a state code or name such as 'PA' or 'Ohio', 'sam' for SAM.gov, or 'us-sba-certifications' for SBA set-aside certifications.

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 states that this is a step-by-step registration guide and that it also returns bid_forms for the selected portal. It does not explicitly differentiate itself from siblings such as list_walkthroughs, but the purpose and returned resource are specific enough for an agent to identify.

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 'Step-by-step registration guide' and the accepted portal values, but there is no explicit guidance on when to use this tool versus alternatives such as list_walkthroughs or check_readiness. It provides enough context to infer the use case but leaves alternative routing to the agent.

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