Skip to main content
Glama

seed_entity_identifiers

Idempotent

Seeds akshare/yfinance stock and World Bank country identifier mappings so agents can resolve entities consistently across data sources.

Instructions

Seed akshare/yfinance (stocks) and worldbank (countries) identifier mappings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare the key traits: not read-only, idempotent, non-destructive, closed-world. The description adds nothing beyond that — it never says what rows get created or overwritten, whether it hits external data endpoints, or what happens on re-run. For a mutating loader, a statement such as "creates identifier mappings; safe to re-run" would be the minimum value-add.

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?

A single short sentence with no filler, and the actionable content (which sources) leads. It is tight but borders on cryptic, since the one sentence carries no surrounding context about effect or safety.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be explained, and with no parameters the contract surface is small. Still, for a mutating seeding operation the agent lacks a plain statement of what gets populated and whether existing rows are affected, which is reasonable to expect even with annotations.

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 tool takes zero parameters (schema coverage reported as 100%), so there is no parameter meaning to convey and the baseline of 4 applies. The parenthetical source labels are the only scheme-level information the agent gets, but nothing is missing from the signature itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ("Seed") and a resource ("identifier mappings") and names the two source families (akshare/yfinance for stocks, worldbank for countries). However, "seed" is internal jargon and the sentence does not differentiate this from nearby siblings such as import_catalog, import_crosswalks, or add_entity_identifier, so the agent must guess which loader applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use condition, no prerequisite call (e.g., whether entities must already exist), and no named alternative or exclusion. The parenthetical data-source labels are the only hint about when this tool is appropriate.

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