Skip to main content
Glama

Read my profile (manufacturers)

get_my_profile
Read-onlyIdempotent

For a manufacturer's agent (needs the supplier token): what the directory stores about your company, and the allowed values for each field.

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

Input Schema

NameRequiredDescriptionDefault
supplier_tokenNoOnly if your client cannot send the Authorization: Bearer header

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a genuine auth note ('needs the supplier token') and hints at return content ('allowed values for each field'), but says nothing about permissions, scope limits, or the response shape for what is an undocumented-return tool.

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?

A single sentence with the audience and auth caveat front-loaded and zero filler. The colon-joined fragment structure is slightly awkward but costs no clarity.

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 tool with no output schema, the description covers audience, auth need, and the nature of the returned data (stored fields and their allowed values). It is nearly sufficient, missing only an explicit contrast with update_my_profile.

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 single parameter is fully documented in the schema ('Only if your client cannot send the Authorization: Bearer header'). The description only repeats that the token may be needed, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 makes clear this reads what the directory stores about your company (a read of your own profile), reinforced by the title 'Read my profile'. The verb is only implied in the body text rather than stated ('what the directory stores'), and it does not explicitly distinguish itself from the sibling update_my_profile, so it stops short of a 5.

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?

It scopes the audience ('For a manufacturer's agent') and flags the supplier-token requirement, implying when this read applies. However, it never states when to use this versus update_my_profile or other profile tools, so usage is only implied.

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