Skip to main content
Glama
Sign In
byline

byline

by indianic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get persona

get_persona

Retrieves an author's full profile—voice, style, bias, and instructions—to generate content in their unique persona.

Instructions

Full author profile — voice, style, bias, and instructions.

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": {
      "slug": "<slug>"
    },
    "name": "get_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation but does not state this explicitly, nor does it mention error handling, permission requirements, or what happens when the slug is invalid. Minimal behavioral context is added.

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?

The description is extremely short and front-loaded, using a dash to present key attributes. It is efficient and avoids waste, though it is a fragment rather than a complete sentence. Every word contributes meaning.

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

Completeness2/5

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

For a tool with one parameter and no output schema or annotations, the description is insufficiently complete. It specifies the general content of the profile but omits the meaning of the input, return format, and any edge-case behavior. An agent would need to guess at slug semantics and result structure.

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

Parameters1/5

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

The schema has 0% description coverage, and the tool description does not mention the 'slug' parameter at all. The agent is left without any explanation of what a slug is or how to supply it, so the description fails to compensate for the missing schema information.

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 'Full author profile — voice, style, bias, and instructions' clearly identifies the tool's output as a comprehensive persona profile, differentiating it from the sibling list_personas tool. Though no explicit verb is present, the resource and scope are specific enough for an agent to infer the retrieval intent.

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 is provided on when to use this tool versus alternatives such as list_personas or other author-related tools. The description gives no context about prerequisites, use cases, or situations where a different tool would be more appropriate.

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