Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_identity

Retrieve a full identity profile by ID, including voice descriptors, writing samples, and contextual fields for analysis.

Instructions

Gets the full profile of a single identity by ID, including voice descriptors, writing samples, and all contextual fields.

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": {
      "identityId": "<identityId>"
    },
    "name": "get_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityIdYesThe ID of the identity to retrieve.
workspaceIdNoWorkspace ID. If not provided, uses your default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description must convey behavior. It explicitly states the returned data includes profile, voice descriptors, writing samples, and contextual fields. This provides good insight into the tool's output, though it omits details about error handling or authorization.

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?

A single sentence that is front-loaded with the core action and specifics. No extraneous words; every part adds value.

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 simple get-by-ID tool with two parameters, the description covers the purpose, resource, and output contents. However, the lack of an output schema means the description should also clarify possible error conditions or missing IDs, which it does not.

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 both parameters have clear descriptions. The tool description adds no further semantic value beyond what the schema already provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Gets' and resource 'full profile of a single identity by ID', and includes specifics like 'voice descriptors, writing samples, and all contextual fields'. It differentiates from sibling tools such as list_identities (list all), create/update/delete identity.

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?

The description implies usage for retrieving a specific identity by ID, but does not explicitly state when to use this tool versus alternatives like list_identities or update_identity. No exclusions or prerequisites are mentioned.

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