Skip to main content
Glama
Sign In
persona-profile-mcp

persona-profile-mcp

by ibeeger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

读取人物画像

get_profile
Read-only

Retrieve a complete persona profile by ID, returning all factual entries with their factId values. Use IDs obtained from search or list operations to pull the full detailed record for a person.

Instructions

按 id 读取完整人物画像，含全部事实条目及其 factId。id 通常来自 search_profiles 或 list_profiles。

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": {
      "profileId": "<profileId>"
    },
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileIdYes

Output Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true, so the safety profile is covered. The description adds that it returns '完整人物画像' including all fact entries and their factIds, which is useful return-context. But it doesn't disclose behavior like pagination, limits, or whether facts are returned in any particular order. With readOnlyHint covering the main concern, a 3 is appropriate.

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 concise sentences, no wasted words. Front-loaded with the primary purpose, followed immediately by source guidance for the id. Every word earns its place.

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?

The tool has an output schema, so return-value explanation is not needed. It has a single required parameter that is adequately explained. Given the low complexity and presence of output schema and readOnlyHint annotation, the description is reasonably complete. It could briefly mention that facts are listed with factIds (which it does), and the provenance of the id is covered.

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 description coverage is 0%, so the description must carry the burden for the single profileId parameter. The description clarifies the id's provenance ('通常来自 search_profiles 或 list_profiles'), effectively explaining what profileId means and where to get it. With only 1 parameter, this compensation is sufficient.

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 states a specific verb+resource ('按 id 读取完整人物画像') and specifies what's returned (全部事实条目及其 factId). It distinguishes itself from sibling read tools but doesn't explicitly name them as alternatives.

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?

The description provides clear context on when to use this tool — it states the id '通常来自 search_profiles 或 list_profiles', which gives the agent guidance on how ids are obtained and implies this is the retrieval tool for a known id. However, it doesn't explicitly state when NOT to use it versus alternatives like search_profiles.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools