Skip to main content
Glama

update_provider_profile

Idempotent

Set your public provider profile. Descriptions are untrusted public text; keep secrets out.

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": {
      "display_name": "<display_name>"
    },
    "name": "update_provider_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionNo
support_urlNo
display_nameYesPublic provider name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by warning that the description text is public and untrusted ('keep secrets out'), which is non-obvious exposure behavior. It does not clarify whether this is a full replace or partial update, or what happens to fields set to null.

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 short sentences with the core action front-loaded followed by the security caveat. Nothing is redundant and no wording could be trimmed without losing meaning.

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 three-field mutation tool the description covers the public-exposure risk but omits update semantics (full replacement vs partial), how null values behave, whether the updated profile is returned (no output schema exists), and any permission requirements. It is adequate but leaves notable gaps for an agent invoking a write operation.

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 only 33% — only display_name carries a description ('Public provider name'). The description partially compensates by characterizing the description field as untrusted public text, but support_url's purpose and format are undocumented in both schema and description, and the maxLength limits are only in the schema.

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 gives a clear verb and resource: 'Set your public provider profile.' Combined with the tool name update_provider_profile, an agent knows this writes profile fields. It stops short of explicitly contrasting itself with the sibling provider_profile reader, so differentiation is inferred 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as being a registered provider, and no reference to alternatives like provider_profile for reading back the profile. Usage is only implied by 'Set your public provider profile.'

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