Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_share_link

Generate a share link for a persona with optional expiration and usage limits to control access.

Instructions

Create a new share link for a persona.

Args: persona_id: The UUID of the persona to share name: Optional name for the link expires_at: Expiration timestamp (ISO 8601) max_uses: Maximum number of uses

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": {
      "persona_id": "<persona_id>"
    },
    "name": "create_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
persona_idYes
nameNo
expires_atNo
max_usesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It states 'create' (implying mutation) but offers no details on side effects, authorization needs, error behavior, or what happens if the persona_id is invalid. The description is minimal in behavioral context.

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 brief and front-loaded with the purpose, followed by a clean parameter list. Every sentence contributes without redundancy. It is well-structured for quick parsing.

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

Completeness3/5

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

The description adequately covers parameter semantics but lacks context about constraints (e.g., persona must exist) and does not mention that an output schema exists (though the agent can infer return structure from it). For a creation tool, more contextual completeness would be beneficial, but it is not severely lacking.

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?

Despite 0% schema description coverage, the description adds meaningful explanations for each parameter: persona_id is 'the UUID of the persona to share', name is 'Optional name for the link', expires_at is 'Expiration timestamp (ISO 8601)', and max_uses is 'Maximum number of uses'. This adds value beyond the schema's property titles.

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?

The description clearly states 'Create a new share link for a persona,' specifying the verb ('create') and resource ('share link') with a target ('persona'). This distinguishes it from sibling tools like update_share_link, delete_share_link, and get_share_link.

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. It does not mention prerequisites (e.g., persona existence), when not to use it, or compare with other sharing-related tools among siblings.

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