Skip to main content
Glama

Crawlora MCP

futgg_fc27_chemistry_style_roles

Read-only

Get the published FC27 chemistry-style/role dataset and return native business metadata and source relationships. Takes no input; manifest versions refresh independently from payload wire versions, and no chemistry or rating outcome is calculated.

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": "futgg_fc27_chemistry_style_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds genuinely non-obvious traits on top: the call is parameterless, manifest versions refresh independently of payload wire versions, and no chemistry or rating computation occurs. The versioning sentence is valuable but jargon-heavy and underexplained.

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?

Two sentences, front-loaded with the purpose before the caveats, and nothing is redundant. The second sentence is dense, stacking three separate caveats with unusual vocabulary, which slightly hurts readability.

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?

An output schema exists, so return values need no explanation here, and the parameterless nature is made explicit. What is missing is any elaboration of what 'native business metadata and source relationships' actually contains or how the independently versioned manifest should be interpreted.

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?

With zero parameters, the baseline is 4, and the description confirms 'Takes no input' consistently with the empty object schema. No further parameter meaning is needed or possible.

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?

Names a specific verb ('Get') and a specific resource ('the published FC27 chemistry-style/role dataset'), plus what it returns ('native business metadata and source relationships'). It is clearly distinguishable from the numeric siblings like futgg_fc27_gg_ratings, though it never names an alternative explicitly.

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?

Usage is only implied: 'Takes no input' tells the agent how to call it, and 'no chemistry or rating outcome is calculated' hints it should not be used when a computed rating is wanted. There is no explicit when-to-use/when-not statement or named sibling to prefer instead.

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