Skip to main content
Glama

Why this person

person_details
Read-onlyIdempotent

What Knowasiak's Discover panel says about one profile: a sentence on why they are worth knowing (their industry, how often they post, how many people found their posts useful and where, people in common on a signed-in connection), a few facts, and whether the member follows them. Use fetch for their full profile and posts.

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": {
      "username": "<username>"
    },
    "name": "person_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesTheir username, with or without @.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile needs no restating. The description usefully adds that mutual connections appear 'on a signed-in connection', hinting that output varies with auth state, but it says nothing about pagination, or what happens when the profile is missing or non-discoverable.

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?

Two sentences, no filler, and the payload contents are front-loaded before the routing hint. The nested parenthetical list is dense but each item corresponds to a real returned field.

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 the work of describing return contents (rationale sentence, facts, follow status) plus the auth-dependent mutual-connections element, which is adequate for a single-parameter read tool. Only error/empty-result behavior is left unstated.

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 `username` parameter is already documented as accepting an optional leading '@'. The description adds no format or edge-case 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 names the specific resource (one profile) and enumerates the distinctive contents of the Discover 'why this person' payload — a rationale sentence, a few facts, follow status — which clearly separates it from a general profile read. The verb is implicit ('what the panel says about') rather than a direct 'get', which keeps it just short of a top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It explicitly routes the full profile and posts use case to the sibling `fetch`, giving a concrete alternative and the condition that selects it. It does not say when this tool should be avoided entirely (e.g., for non-discoverable accounts), but the alternative guidance is clear.

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