Skip to main content
Glama
Sign In

ViralMint

by net.viralmint
OverviewDiscussionsAdmin

Save a Persona

persona_create

Free. Saves 1-5 staged photos of one person as a Persona (at most 5 Personas). consent: true only when the user has told you this is them, or that they have the person's permission.

Args: name: 1-120 chars. photo_attachment_ids: 1-5 attachment ids from upload_finish or stage_library_item. consent: must be true. notes: optional.

Returns: {ok, persona:{id, name, photo_count, ...}}. Errors: photo_missing, too_many.

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": {
      "name": "<name>",
      "photo_attachment_ids": "<photo_attachment_ids>",
      "consent": "<consent>"
    },
    "name": "persona_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
notesNo
consentYes
photo_attachment_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false) it discloses cost ('Free'), an account-level quota (5 Personas), a consent/authorization requirement, and the error codes photo_missing and too_many. It does not say whether the save is reversible or how quota interacts with persona_delete, leaving a small gap.

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?

Front-loaded with cost and the core action, then cleanly sectioned into Args and Returns. Minor waste in restating the name length and the 1-5 count already enforced by the schema.

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?

For a 4-parameter mutation with no output schema and no annotations covering behavior, it supplies the return shape, named error cases, quota, cost, and the prerequisite attachment source. An agent has everything needed to call it correctly.

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?

With 0% schema description coverage the description carries the burden and mostly does: it constrains name length, ties photo_attachment_ids to upstream tools and a 1-5 range, and explains the meaning of consent as an authorization assertion. notes is only labeled 'optional' with no guidance on useful content.

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?

States a specific verb and resource ('Saves 1-5 staged photos of one person as a Persona') plus concrete scope limits ('at most 5 Personas'), which clearly separates it from staging tools like persona_stage and listing tools like persona_list.

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

Usage Guidelines4/5

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

Gives a real precondition chain ('attachment ids from upload_finish or stage_library_item') and an explicit rule for when consent may be true. It stops short of naming sibling alternatives or stating when not to create a Persona, so it is strong but not complete routing guidance.

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

All ViralMint toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources