Skip to main content
Glama
Sign In

Foliyo

by io.foliyo
OverviewDiscussionsAdmin

Save a group of people you send to

save_audience
DestructiveIdempotent

Save or replace a named recipient group. The complete supplied member list replaces the saved list; previously published recipient links remain valid. This operation stores names and optional email addresses without sending email.

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": {
      "id": "<id>",
      "members": "<members>"
    },
    "name": "save_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShort handle, e.g. "acme-team". Reusing one updates it in place.
labelNoWhat to call it, e.g. "The Acme team". Defaults to the id.
membersYesThe people. An email is what lets them be notified and named in the report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / members / items / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it clarifies that the complete member list replaces the saved list, that previously published recipient links remain valid, and that no email is sent. These details are consistent with destructiveHint=true and idempotentHint=true and help the agent understand the mutation's exact effects.

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 three tight sentences with no waste. It front-loads the core action and follows with the most important behavioral details.

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 rich annotations and full schema coverage, the description is complete for a save mutation. It covers replacement semantics, link stability, and the no-email side effect, with no output schema needed.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents id, label, and members thoroughly. The description adds useful context about replacement and email addresses, but does not add per-parameter syntax or constraints beyond what the schema provides.

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 states a specific verb and resource: "Save or replace a named recipient group." It clearly separates creation/update from retrieval or deletion, but does not explicitly name sibling tools like get_audience or delete_audience, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description implies the tool's use case by saying it saves or replaces a recipient group, and notes that reuse of the id updates in place. However, it gives no explicit when-to-use guidance, exclusions, or alternatives such as get_audience or delete_audience.

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

All Foliyo 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