Skip to main content
Glama

FindMyBids

Update my business profile

save_profile
DestructiveIdempotent

Save or update the user's business profile (merged into what's saved). Fields: company_name, home_state, naics (list), certifications (list), registrations ({"SAM": {"status": "active", "expires": "YYYY-MM-DD"}, "PA": {"status": "active"}}), insurance (dollar limits), bonding, licenses, states_qualified.

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": {
      "profile": "<profile>"
    },
    "name": "save_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the safety profile is covered. The description adds genuine value with the merge semantics ('merged into what's saved'), clarifying that a call is additive rather than a full replacement. It does not, however, explain the destructive side of the annotations — whether merging can overwrite existing values or how conflicts between supplied and stored fields resolve.

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?

Two sentences: the first states the action and merge behavior, the second is a compact field inventory. The operation is front-loaded ahead of the field list, and every clause contributes information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single nested object parameter with zero schema documentation and no output schema, the description does a reasonable job enumerating top-level fields and one nested structure. It remains incomplete on the shapes of several list/scalar fields and on the return value, so an agent can form the call but may need to guess at value formats.

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?

Schema coverage is 0% and the single `profile` parameter is an untyped object with additionalProperties=true, so the description carries the full burden — and it largely does, enumerating company_name, home_state, naics, certifications, registrations, insurance, bonding, licenses, and states_qualified, even sketching the nested registrations shape. It stops short of giving types or formats for several fields (insurance 'dollar limits', bonding, licenses, states_qualified), leaving ambiguity about accepted value shapes.

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 opens with a specific verb and resource: 'Save or update the user's business profile', which clearly separates it from the read-only sibling get_profile. It does not explicitly name get_profile as the read counterpart, so sibling differentiation is implied rather than stated.

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?

The phrase 'merged into what's saved' implies this can be called for partial updates, which is useful when-to-use context. However, there is no explicit guidance on prerequisites (e.g., must a profile exist first), no mention of when to prefer get_profile, and no statement about what happens to fields omitted from the call.

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