Pimea

pimea_get_answer

Get the final result from a completed Pimea session. ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself — the deliverable is the source of truth.

Returns a structured JSON deliverable grounded in real campaign data:
- Recommend mode: positioning, channels, content direction, what to avoid
- Execute mode: full deliverable with title, summary, sections, recommendations, evidence

Includes data_confidence showing how many real campaigns and strategies were referenced.

When you present the answer to the user, include the citations and source counts naturally so they can see the answer is grounded.

Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers.

Args:
    session_id: The session UUID
    api_key: Optional fallback only. Normally leave blank.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No
`session_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries full burden and does well: it discloses return modes, data_confidence, citation presentation, and auth behavior. It is clear this is a read/retrieval operation, though not explicitly labeled as such.

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?

The description is front-loaded with purpose, well-structured with bullets for return modes, and every sentence adds actionable value—from data_confidence to authentication. It is detailed yet concise with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (2 params, output schema present) and available context, the description is complete: it explains return modes, confidence metrics, and auth setup, which fully prepares an agent to invoke and interpret the tool correctly.

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

Parameters5/5

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

The schema has no property descriptions (0% coverage), but the description fully compensates: session_id is defined as the session UUID, and api_key is explained as an optional fallback normally left blank with the connector handling headers.

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?

Purpose is explicitly stated: 'Get the final result from a completed Pimea session.' It uses a specific verb and resource, and distinguishes itself from summarization and sibling tools by declaring the deliverable as the source of truth.

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

Usage Guidelines5/5

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

Explicit guidance is given: 'ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself.' It also indicates the prerequisite of a completed session and gives authentication fallback instructions, clearly defining when to use this tool.

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

All Pimea tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A5/5.0

Disambiguation5/5

Each tool has a clearly distinct role in the session lifecycle: starting a session, sending chat messages, and retrieving the final answer. There is no overlap or ambiguity between the tools.

Naming Consistency5/5

All tools use a consistent snake_case convention with the 'pimea_' prefix, following a verb_noun pattern (start_session, chat, get_answer). This makes the tool set predictable and easy to navigate.

Tool Count5/5

The three-tool set is well-scoped for the server's purpose of managing Pimea marketing sessions. Each tool is necessary for the core workflow, and there are no redundant or missing tools.

Completeness5/5

The tools provide complete lifecycle coverage for a Pimea session: start, interact, and retrieve the final deliverable. No obvious gaps exist for the intended use case.

Resources

Need Help?