Skip to main content
Glama
Sign In
superpos-mcp

superpos-mcp

Official
by Superpos-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

superpos_get_persona

Fetches the agent's assembled persona and system prompt from Superpos, including SOUL, RULES, STYLE, MEMORY, pre-assembled server-side.

Instructions

Fetch this agent's assembled persona/system prompt from Superpos (SOUL, RULES, STYLE, MEMORY, ... pre-assembled server-side).

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": "superpos_get_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, description should disclose more behavioral traits. Only states it fetches pre-assembled persona, implying read-only but doesn't explicitly state lack of side effects, rate limits, or permissions needed.

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?

Single sentence, no fluff. Front-loaded with action and resource description. Efficiently communicates purpose and content.

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?

Since output schema exists, description doesn't need to detail return format. Provides enough context about what the persona contains. Slight lack of detail on how the assembled persona is structured, but acceptable.

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?

No parameters so baseline is 4. Description adds value by enumerating the components of the persona (SOUL, RULES, STYLE, MEMORY), giving context beyond the empty schema.

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?

Clearly states verb 'Fetch' and specific resource 'persona/system prompt', with details on contents (SOUL, RULES, STYLE, MEMORY). Distinct from siblings like superpos_get_knowledge which fetches individual knowledge items.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Does not mention when not to use it or compare with sibling tools like superpos_whoami.

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