Skip to main content
Glama
codal-mcp

codal-mcp

by sepehr071

Find a company on Codal

cd_company
Read-onlyIdempotent

Find companies and funds on codal.ir by Persian symbol or name to get exact symbols, market, industry, and type for Codal disclosure searches.

Instructions

Find companies and funds on codal.ir by symbol or name, with their market, industry and type.

Use it to get the exact symbol for cd_search_letters and cd_financial_years. Exact matches first, then prefix, then name contains; listed before unlisted. matched is the total number of hits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "cd_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax companies.
queryYesPersian symbol or part of the name, e.g. فولاد.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Most companies to return."New value: +"Max companies."
    • changedInput schema / properties / query / description
      Previous value: -"Trading symbol or part of the company name, in Persian, e.g. فولاد or فولاد مبارکه."New value: +"Persian symbol or part of the name, e.g. فولاد."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavior the annotations cannot: the match-ranking order (exact, then prefix, then name-contains, with listed before unlisted) and the meaning of the `matched` field as the total hit count. It does not discuss truncation when `limit` cuts off results, which is the one remaining behavioral question.

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 short paragraphs with zero filler: the first states what is found and what comes back, the second states why to call it and how results are ordered. The most decision-relevant routing information is front-loaded.

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 two-parameter read-only lookup with no output schema, the description covers purpose, workflow position, match ordering, and the one notable response field (`matched`). Nothing an agent needs in order to call this correctly and interpret the top result 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 coverage is 100%, so both `query` (Persian symbol or name fragment, with an example) and `limit` (1-50, default 10) are already documented in the schema — baseline 3 applies. The description's ranking-order sentence does add semantic meaning about how `query` is matched, but it stops short of clarifying that lower-ranked matches still appear when the top hit is not exact.

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?

States a specific verb (Find) and resource (companies and funds on codal.ir) plus the searchable fields (symbol or name) and the payload fields returned (market, industry, type). It also positions itself against siblings by naming cd_search_letters and cd_financial_years as downstream consumers, so an agent knows this is the entity-resolution step rather than a document search.

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

Usage Guidelines4/5

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

"Use it to get the exact `symbol` for cd_search_letters and cd_financial_years" gives a concrete workflow condition for selecting this tool. There are no competing company-lookup siblings to exclude, so the absence of an explicit when-not clause is a minor gap rather than a real ambiguity.

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