Skip to main content
Glama

FindMyBids

My business profile

get_profile
Read-onlyIdempotent

The user's saved business profile used by check_readiness (same as findmybids.com/account/business), plus the template of fields it understands.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the dependency relationship with check_readiness, the external source of truth for the data, and the fact that a field template accompanies the profile. It does not state what is returned when no profile has been saved, which keeps it below the top band.

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 sentence with no filler. The primary subject (the saved profile) is front-loaded and the two supporting clauses — the consumer and the field template — are compact and each carry information an agent would otherwise have to discover.

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 does meaningful work by indicating the response has two parts: the profile itself and a template of understood fields. For a zero-parameter read tool this is close to sufficient; the only real gap is the empty/no-profile case and any indication of how the template differs from the saved values.

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

Parameters4/5

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

There are zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline for a no-parameter tool applies; the description's mention of the field template usefully frames what the object contains even though no inputs exist.

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 — the user's saved business profile — and adds a second, non-obvious payload: the template of fields it understands. A parenthetical maps it to a concrete UI location (findmybids.com/account/business), which pins down scope. It stops short of contrasting explicitly with save_profile, so it is clear but not fully differentiated from siblings.

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 rather than stated: the agent learns the profile is consumed by check_readiness, which hints at reading it before a readiness check, but there is no explicit 'use this instead of X' or 'call save_profile to modify'. A caller must infer the read-before-check pattern and the empty-profile case on its own.

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