Skip to main content
Glama
Sign In

FanZero — indie game distribution

by app.fanzero
OverviewDiscussionsAdmin

Add pact

add_pact

Offers one more revenue-share pact on one of your games. Same rules for every pact: one influencer at a time, 4 weeks from the first proposed action date, share_pct% of net revenue from every store. Get the terms from your human.

Input Schema

NameRequiredDescriptionDefault
actionYesWhat the influencer (a streamer, YouTuber or TikToker) does: livestream, video, short, post or playtest
api_keyNoStudio API key. Only needed when the connection does not send Authorization: Bearer <key> (for example in the session that created the studio): then pass it on every call.
game_idYesGame id (gm_…) or slug
share_pctYesPercent of the game's net revenue from every store, for 4 weeks from the earliest date in the influencer's approved action plan. In percent: 10 means 10%. Above 0, at most 50. The window length is fixed.
requirementNoConcrete requirement, e.g. "60+ min live, game title in stream title". Left out, a generic one for the action is used.
min_audienceNoOptional follower floor. Followers are self-reported; pitches below it are flagged (below_min_audience), not blocked.

Output Schema

NameRequiredDescriptionDefault
pactYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"What the streamer (or YouTuber, TikToker) does: livestream, video, short, post or playtest"New value: +"What the influencer (a streamer, YouTuber or TikToker) does: livestream, video, short, post or playtest"
    • changedInput schema / properties / share_pct / description
      Previous value: -"Percent of the game's net revenue from every store, for 4 weeks from the earliest date in the creator's approved action plan. In percent: 10 means 10%. Above 0, at most 50. The window length is fixed."New value: +"Percent of the game's net revenue from every store, for 4 weeks from the earliest date in the influencer's approved action plan. In percent: 10 means 10%. Above 0, at most 50. The window length is fixed."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world. The description adds real business semantics beyond that: one influencer at a time, a fixed 4-week window from the first proposed action date, and share of net revenue across every store. It does not clarify what a duplicate call does given idempotentHint=false, which is the main remaining gap.

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?

Three short sentences, front-loaded with the operation then the invariant rules then the prerequisite. Every clause carries information and nothing is repeated from the schema verbatim.

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?

With annotations covering the safety profile, an output schema, and full schema description coverage, the description only needs to supply the pact's business invariants — which it does (one influencer, fixed 4-week window, revenue scope, human-sourced terms). Nothing essential to correct invocation 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%, so every parameter including api_key, requirement, and min_audience is already documented at the field level. The description only restates the share_pct/window rule that the schema already spells out, so it adds marginal value; the baseline 3 applies.

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?

States a specific verb and resource: 'Offers one more revenue-share pact on one of your games,' which reads unambiguously as a creation operation. It does not explicitly contrast with close_pact or the other pact-lifecycle siblings, so sibling differentiation is only implied.

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?

'Get the terms from your human' is a concrete precondition telling the agent not to invent share_pct/action values autonomously. Usage context is clear, but no exclusion or alternative-routing guidance is offered (e.g., when to use close_pact instead).

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

All FanZero — indie game distribution toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources