Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_manager

Retrieve a coach's profile—nationality, birth date, preferred formation, teams, and career win/draw/loss and goals—using a numeric SofaScore manager ID.

Instructions

SofaScore manager detail. Returns a manager's (coach's) profile (nationality, birth date, preferred formation, current team and teams, and the career win/draw/loss and goals record). Get a manager id from sofascore-search results of type manager.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore manager id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It implies a read via 'returns' and discloses the returned data shape, but says nothing about read-only status, permissions, rate limits, or error behavior for missing ids.

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?

Two tight sentences, front-loaded with purpose, followed by the id-sourcing hint. No filler.

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?

No output schema exists, so the description correctly compensates by listing return fields. For a single-parameter read tool this is nearly complete; only the absent when-to-use guidance and behavioral notes hold it back from a 5.

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?

Schema coverage is 100% and defines `id` as a numeric SofaScore manager id. The description adds provenance beyond the schema by pointing to sofascore-search with type `manager` as the id source, which meaningfully helps an agent obtain a valid value.

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 ('returns a manager's profile') and enumerates the payload fields (nationality, birth date, formation, teams, W/D/L record). It is clearly distinguished from sibling helpers like sofascore_manager_events, though it does not name them 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?

Provides the key prerequisite for the id (get it from sofascore-search results of type `manager`), which is genuinely useful context. However it never states when to use this tool versus sofascore_manager_events or other manager-related siblings, so usage is only implied.

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

Deploy Server

Other Tools