Skip to main content
Glama
Sign In

VeriApi.Pro

by io.github.veriapipro
OverviewDiscussionsAdmin

Turkish football league standings

spor_puan_durumu
Read-onlyIdempotent

Returns the current table of Turkish professional leagues (Süper Lig, 1. Lig, 2. Lig groups, 3. Lig groups): position, played, won, drawn, lost, goals, goal difference and points, including point deductions. Paid plans only.

Endpoint: GET /v1/spor/puan-durumu. Requires a paid plan (free plan returns 403). Costs 2 request units per call. Read-only; JSON in Turkish with source and guncelleme (updated at) fields.

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

Input Schema

NameRequiredDescriptionDefault
ligNoComma-separated league codes: super-lig, 1-lig, 2-lig-beyaz, 2-lig-kirmizi, 3-lig-1, 3-lig-2, 3-lig-3; '2-lig' / '3-lig' for all groups. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the paid-plan requirement, the 403 behavior on free plans, the cost of 2 request units per call, the HTTP endpoint, and that the response is read-only Turkish JSON with source and update fields. This is substantial behavioral context for an API tool with no output schema.

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?

The description is front-loaded with purpose and return fields, then adds operational details, and every sentence carries useful information. There is minor redundancy between 'Paid plans only' and 'Requires a paid plan', but it remains efficient overall.

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 one-parameter read-only standings tool with no output schema, the description covers what is returned, league scope, auth/payment requirements, call cost, and response format. Nothing essential for 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%, and the schema already documents the league codes, group aliases, and omission behavior. The description mentions the leagues covered but does not add parameter syntax or meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb and resource: returns the current standings table for Turkish professional leagues. It names the covered leagues and the exact fields returned, so an agent can distinguish this from unrelated sibling tools immediately.

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 implied by 'current table' and the paid-plan restriction, but there is no explicit when-to-use guidance versus alternatives or when-not-to-use guidance. The absence of a direct standings sibling limits the practical ambiguity, but the description still leaves routing to inference.

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

All VeriApi.Pro toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources