rasmio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RASMIO_MCP_PROXY | No | Optional HTTP proxy URL, or a comma-separated list of proxy URLs. System proxy settings are ignored. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rs_companyA | Registry profile of one Iranian company: basics, board and CEO, shareholders, licenses, capital history, ads. Basics: founding date, status, legal form, registration number, economic code, capital in Rial, activity, address and postal code. Board rows give person_id for rs_person and ad_id for rs_ad (the gazette notice that appointed them). Anonymous visitors may open only a few profiles per IP address every few days; a clear error says when that limit is reached (search still works then). Dates are Persian (1404/06/26). |
| rs_adA | Full text of one official gazette (روزنامه رسمی) ad: board changes, capital changes, founding, liquidation. People's national codes in the text are shortened to their first 6 digits, as the site shows them. |
| rs_personA | Companies one person manages, sits on the board of or audits, with role dates and their latest gazette ads. current=false marks a finished term. ad_id points to the gazette notice behind each role (open with rs_ad); company_id opens the company with rs_company. Contact details and national codes are not returned. |
| rs_productA | One registered product: full specs (HS/ISIC codes, brand, maker, country), category and comparable suppliers. similar_suppliers lists other companies with the same or a close product (company_id for rs_company). The category_slug works as product_category in rs_search_companies to find every supplier of the category. |
| rs_ipB | Registration details of an Iranian trademark, patent or industrial design: numbers, date, owner, description. |
| rs_search_companiesA | Search Iranian companies by name or activity with filters; returns national ids for rs_company. Each result has the company's national id (company_id, شناسه ملی), name, age/capital summary, CEO and up to 5 licenses. Combine filters freely, e.g. active software companies in Isfahan with capital over 10 billion Rial. Next: rs_company(company_id) for the full registry profile (board, shareholders, gazette ads). |
| rs_searchA | Search people (board members, managers), products, registered brands or patents and industrial designs. People results give person_id for rs_person and the companies they sit in. Products give product_id for rs_product and the supplier's company_id. Brands and patents give ip_id for rs_ip. For companies use rs_search_companies (it has filters). |
| rs_optionsA | List the ids and names the search filters take: legal forms, licenses, product categories, brand classes. Use the returned id/slug in rs_search_companies (company_type, license_id, product_category, province, city) or rs_search (product_category, brand_class). counts are how many companies or products carry each value. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct role: entity detail lookups (rs_company, rs_ad, rs_person, rs_product, rs_ip), scoped search (rs_search_companies vs rs_search), and filter metadata (rs_options). The descriptions explicitly cross-reference each other and clarify when to use generic search versus the company-specific search, so an agent can reliably select the right tool.
All tools share a consistent rs_ prefix and snake_case style, with entity getters named rs_<entity> and search tools named rs_search*. The main minor deviation is mixing noun-only getters (rs_company) with verb-based searches (rs_search_companies, rs_search) and the plural in rs_search_companies, but the pattern remains readable and predictable.
Eight tools cleanly cover the server's scope without redundancy: five entity lookups, two search entry points, and one options helper. This is well within the ideal 3-15 range and each tool earns its place.
The surface covers company, person, ad, product, and IP lookups plus both general and filtered search with filter metadata, which is strong for a read-only registry. Minor gaps exist, such as no direct tool to list a company's products or search gazette ads independently, but agents can work around these via product categories and linked ad_ids.