Skip to main content
Glama

Coline

Person's profile

get_person_profile
Read-onlyIdempotent

Reads a teammate's profile as Messages shows it: name, title, status, local time and how to reach them.

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": {
      "workspace": "<workspace>",
      "userId": "<userId>"
    },
    "name": "get_person_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds the useful nuance that the data is presented the way Messages renders it, plus the field set, but says nothing about permission/visibility limits when reading another person's profile or error behavior for an unknown userId.

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 front-loaded sentence that packs the verb, resource, source-of-truth and field list with no filler. The colon-delimited field enumeration is easy to scan. Only the slightly colloquial "as Messages shows it" costs a bit of precision.

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?

An output schema exists, so return values need no explanation, and the annotations fully cover the safety profile. However, for a tool with two required parameters and a look-alike sibling, the definition omits userId semantics and disambiguation, which an agent genuinely needs before calling it correctly.

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

Parameters2/5

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

Schema coverage is only 50%: `workspace` is documented in the schema, but `userId` has no description anywhere. The prose does not mention either parameter, does not say whether userId is a UUID, email or handle, and does not clarify workspace scoping. With half the parameters undocumented, the description fails to compensate.

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 verb ("Reads") and resource ("a teammate's profile") and even enumerates the payload: name, title, status, local time, contact details. That is far beyond a restatement of the name. It stops short of a 5 because it never distinguishes itself from the sibling `get_profile`, leaving an agent to guess which of the two profile readers to call.

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: call this when you need a teammate's profile information, and "as Messages shows it" hints at the authoritative source. There is no explicit when-to-use, no when-not-to-use, and no mention of the obvious alternative `get_profile`, which is a real risk given the near-identical names.

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