Skip to main content
Glama

SPXI-gnΩsis

by dev.spxi
OverviewDiscussionsAdmin

Price a whole article or a commission (free)

get_quote

Use to price work before paying: a whole Wikipedia article (article: its link or title, or oldid), read sentence by sentence at a tier, or a commission on an object (object with kind entity or operator, name, and for an operator its strings; commission construct or open): construct gives an entity the encyclopedia holds an alternative to its article, and one it lacks its first account. Or random open (a random article's cited sentence, read at tier check or opening) or random construct (a random Wikipedia article as an alternative, or an object the archive names with no /non entry); the quote says what was picked. Free; returns a quote_id with each deliverable, its line and the maximum, or, for a commission, a quote_id whose price appears at order_status within minutes. Pay a quote over x402 at POST /v1/openings/{quote_id}, or have a person pay with card_checkout. For one sentence use open_sentence; to see whether an object already exists use find_entry first.

Input Schema

NameRequiredDescriptionDefault
poolNofor random construct: a random Wikipedia article, constructed as an alternative from the sources it cites, or an object the archive names with no /non entry; omitted, chosen at random
tierNocheck: two passes on the small model; opening (default): two separately generated readings; commission: opened, then the archive consulted and a public /non row composed; portable: the commission and its knowledge object as a package
oldidNoa Wikipedia revision id, in place of article
objectNofor a commission on an object: {kind: "entity" | "operator", name, description?, strings? (an operator's phrases), sources? (links)}
randomNolet the service pick: open, a random Wikipedia article's cited sentence; construct, a random object (see pool). The quote carries the pick as random
articleNoan English Wikipedia article's link or title; its current revision is pinned
commissionNoconstruct: compose the object from the archive and its sources, an alternative where an account exists; open: read an AI answer seated in the Capture Registry for the name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / commission / description
      Previous value: -"construct: compose the object from the archive and its sources; open: read an AI answer seated in the Capture Registry for the name"New value: +"construct: compose the object from the archive and its sources, an alternative where an account exists; open: read an AI answer seated in the Capture Registry for the name"
    • addedInput schema / properties / pool
      Added value: +{
+  "description": "for random construct: a random Wikipedia article, constructed as an alternative from the sources it cites, or an object the archive names with no /non entry; omitted, chosen at random",
+  "enum": [
+    "wikipedia",
+    "archive"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / random
      Added value: +{
+  "description": "let the service pick: open, a random Wikipedia article's cited sentence; construct, a random object (see pool). The quote carries the pick as random",
+  "enum": [
+    "open",
+    "construct"
+  ],
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / article
      Added value: +{
+  "description": "an English Wikipedia article's link or title; its current revision is pinned",
+  "type": "string"
+}
    • addedInput schema / properties / commission / description
      Added value: +"construct: compose the object from the archive and its sources; open: read an AI answer seated in the Capture Registry for the name"
    • addedInput schema / properties / object / description
      Added value: +"for a commission on an object: {kind: \"entity\" | \"operator\", name, description?, strings? (an operator's phrases), sources? (links)}"
    • addedInput schema / properties / oldid / description
      Added value: +"a Wikipedia revision id, in place of article"
    • addedInput schema / properties / tier / description
      Added value: +"check: two passes on the small model; opening (default): two separately generated readings; commission: opened, then the archive consulted and a public /non row composed; portable: the commission and its knowledge object as a package"
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and adds substantial behavior: the tool is free, returns a quote_id with each deliverable and its line/maximum, and for commissions returns a quote_id whose price appears at order_status within minutes. It also explains payment paths via x402 or card_checkout. It does not discuss authentication or rate limits, but the core operational behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense run-on paragraph with deeply nested clauses, making it hard to parse despite front-loading the purpose. Much of the content is relevant, but the structure is poor and the phrasing forces the reader to untangle multiple modes in one sentence.

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 complex, seven-parameter tool with no annotations and no output schema, the description covers the main modes, return shape, payment flow, and sibling alternatives. It leaves some gaps around required parameter combinations and authentication, but it is substantially complete for an agent to invoke the tool correctly.

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 all seven parameters, including enum meanings and the nested object shape. The description reiterates many of these meanings and shows how modes combine, but it adds little parameter-level detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a specific verb and resource: "Use to price work before paying: a whole Wikipedia article ... or a commission on an object ... Or random open ... or random construct." It clearly distinguishes the main pricing modes and later differentiates from open_sentence and find_entry, so an agent can identify what the tool does without opening the schema.

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 states the primary use case (price work before paying) and names alternatives: "For one sentence use open_sentence; to see whether an object already exists use find_entry first." It also describes when a commission quote's price appears at order_status and how payment occurs, covering both selection and follow-up.

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

All SPXI-gnΩsis toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources