Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

platform_info

Read-onlyIdempotent

Return OnlyChili's platform summary, 8 supported languages, public browse hubs, creator economics, compliance policy, and machine-readable discovery URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "platform_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds genuine value beyond that by disclosing what the payload contains (languages, hubs, economics, policy, discovery URLs), which matters since there is no output schema. The lower-than-max score reflects that it says nothing about response size or shape beyond the topic list.

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?

It is a single front-loaded sentence with no filler or hedging, and the core purpose appears in the first few words. The enumeration is dense but each item maps to real content, though quantifying '8 supported languages' is a detail that arguably belongs in the return payload rather than the description.

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 zero-parameter, read-only, closed-world overview tool, the description covers everything an agent needs: what it returns and, implicitly, that it is a fixed no-argument summary. With annotations carrying the safety profile and no output schema to defer to, enumerating the content categories in the description is the right compensating move.

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?

The input schema is an empty object with additionalProperties=false, so there are zero parameters to explain; the baseline for a no-parameter tool is 4. The description correctly implies the tool is argument-free by describing it purely as a retrieval of a fixed summary.

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 ('Return OnlyChili's platform summary') and then enumerates the content categories covered: languages, browse hubs, creator economics, compliance policy, and discovery URLs. That scope is unmistakably distinct from the video/channel-centric siblings (get_video, list_series, search_videos), so an agent can route to it without opening a schema.

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 usage is only implied: an agent can infer 'call this for a general orientation to the platform.' There is no explicit when-to-use statement, no when-not-to-use, and no named alternative (e.g., use get_channel for a specific publisher). As a zero-parameter read tool the risk is low, but the guidance is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources