Skip to main content
Glama
Sign In

FPL Copilot

by com.fplcopilot
OverviewDiscussionsAdmin

Share this card

create_share_link

App-only. The fplcopilot card's Share button calls this with the card's share token; it publishes that card, as this server made it, to a public fplcopilot.com page and returns the link. Nothing else can be published.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe share token of a card this server made

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / component
      Removed value: -{
-  "description": "The card's component, e.g. rating_card",
-  "maxLength": 40,
-  "title": "Component",
-  "type": "string"
-}
    • removedInput schema / properties / data
      Removed value: -{
-  "additionalProperties": true,
-  "description": "The card's data object",
-  "title": "Data",
-  "type": "object"
-}
    • removedInput schema / properties / token / anyOf
      Removed value: -[
-  {
-    "maxLength": 64,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / token / default
      Removed value: -null
    • changedInput schema / properties / token / description
      Previous value: -"The card's share token (from the result's _meta)"New value: +"The share token of a card this server made"
    • addedInput schema / properties / token / pattern
      Added value: +"^[0-9a-f]{40}$"
    • addedInput schema / properties / token / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "component",
-  "data"
-]New value: +[
+  "token"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that publication is to a public fplcopilot.com page, that the card is published 'as this server made it', and that the call returns the link. It does not state whether links can be revoked, whether repeated calls create distinct public pages, or what happens with stale tokens, which are meaningful gaps for a non-idempotent write operation.

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 short, front-loads the app-only constraint, and avoids generic filler. The final sentence ('Nothing else can be published') partly restates the schema's 'a card this server made', so it is not maximally tight.

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

Completeness4/5

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

For a single-parameter tool with annotations and no output schema, the description covers the key context: caller, target, public exposure, and return value. It could be more complete by describing repeat-call behavior and link lifecycle, but nothing essential to invoking it is missing.

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% and the single token parameter already has a regex and description. The tool description reinforces that it is the card's share token and belongs to a card this server made, but adds little semantic detail beyond the schema.

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 uses a specific verb (publishes) and resource (the fplcopilot card) and states the outcome: a public fplcopilot.com link is returned. It also scopes the operation tightly with 'App-only' and 'Nothing else can be published', making it unmistakable versus the many read-oriented sibling tools.

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?

It explicitly says the tool is invoked by the card's Share button with the card's share token, and rules out publishing anything else. That gives clear when-to-use and when-not-to-use guidance, even though there is no similarly named sibling alternative to route away from.

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

All FPL Copilot 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