465,824 tools. Updated 2026-08-19 07:16
"Elm" matching MCP tools:
- Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's trigger/conditions/actions, delete and recreate.Connector
- Change an existing pipeline by key or pl_ id. action=rename changes its display `name` and/or its key (pass `new_key`) - deals link by internal id, so they follow a re-key automatically; action=set_default makes it the workspace default; action=delete removes it (fails if deals still use it - move them first). To read one, use relm_get_pipeline.Connector
- Returns a time series or aggregate statistics for a single Tesouro Direto bond over a date range. Required paper selector: this tool queries ONE bond, not a whole product family. Always provide exactly one of `maturityDate`, `maturityYear`, or `conversionYear`. Use `conversionYear` only for `renda-mais` / `educa-mais`; for Prefixado/IPCA+/Selic/IGPM use `maturityDate` or `maturityYear`. If the user did not specify a maturity, call `catalog_list` first or ask for the maturity. Two modes via `aggregate`: - 'none' (default): raw daily points, each with `investorBuy: { rate, price }` and `investorSell: { rate, price }`. Sub-sample with `step`: 'daily' / 'weekly' / 'monthly'. Max 10000 points; truncated=true if exceeded. Optional pagination: `limit` (1-200) + `offset` + `order` ('asc'|'desc') — response then carries `meta.page { total, offset, limit }` and the 10000-point cap does not apply. - `'stats'`: per side (`investorBuy` / `investorSell`) over the window: min/max/avg/count for rate and price, plus rate-only percentiles `p25`/`p50`/`p75` (nearest-rank — actually published values), `last` (most recent rate) and `lastPercentile` (0-100: share of the window strictly below `last`). Compact single-object response — prefer this for "is today's rate high?" questions. Field semantics: - `investorBuy` — investor PURCHASE side (STN's Taxa de Compra / PU de Compra). This is the standard quoted rate. - `investorSell` — investor SELL-BACK side (STN's Taxa de Venda / PU de Venda). Normally investorSell.rate > investorBuy.rate. Use when the user asks for a time series or aggregate stats (e.g. rate evolution over 12 months, min/max rate in a year). **Rates are decimal fraction strings** (same as `price_history_lookup`, `simulate_bond`, `live_quotes_lookup`).Connector
- Looks up **live** quotes for Tesouro Direto bonds (sourced from the TD website, not STN CSV). Use for current indications only. Each query requires `productId` plus **exactly one** year field — **`maturityYear` is required for all products except renda-mais/educa-mais**; for renda-mais/educa-mais use `maturityYear` (calendar maturity year) OR `conversionYear` (label year on the bond name, e.g. 2027 for 'Educa+ 2027') — never both. Omitting the year field will error. Each result has optional `investorBuy` and `investorSell` objects with `{ rate, price }` — the two sides are independent, so one may be present without the other. When `found` is true there is also an optional `fetchedAt` — ISO-8601 UTC from the last site scrape. Field semantics: - `investorBuy` — investor PURCHASE side: rate and price at which the investor buys from the Treasury. - `investorSell` — investor SELL-BACK side: rate and price at which the investor sells back to the Treasury. Normally investorSell.rate > investorBuy.rate. Always consult `catalog_list` to check if the bond is currently available for purchase or sale by Tesouro Direto. `found: true` means at least one of `investorBuy` / `investorSell` is present — each side may be absent independently, so always check which one came back (if you need a single rate and `investorBuy` is missing, use `investorSell`). `found: false` means **neither** side is present. Possible causes: outside BRT market hours (nights/weekends/holidays), the bond is not currently offered by Tesouro Direto, the year identifier does not match an active offering, or the stored quotes are invalid. When `found` is false fall back to `price_history_lookup` / `price_history_series` for the latest official STN rate. **Rates are decimal fraction strings** (e.g. `'0.0753'` = 7.53% a.a.) — same convention as `price_history_*` and `simulate_bond`.Connector
- PRE-ACTION Bulk Processing ($0.10). Evaluates a list of items in one call; each item is a dict shaped {"response": str, "policy"?: str}, where policy defaults to "default" if omitted and may be any built-in policy name (default, strict, anti_jailbreak, safety, content_quality). Each item gets its own independent COMMIT/NO_COMMIT verdict via the same logic as the matching single-item evaluate_* tool; results are returned in input order under `results`, plus a shared `batch_id`. Capped at 200 items per call — oversized batches are rejected. Use this instead of multiple single-item evaluate_* calls when checking several responses — optionally against different policies — in one priced call rather than paying per item separately.Connector
- WHEN: you know the EXACT object name. Triggers: user gives an exact name like 'SalesTable', 'CustTable', 'VendInvoiceJour', any PascalCase D365 object name. Get complete details: all fields, methods, relations, indexes, source code, and metadata. COST NOTE: this returns the FULL object and can be very large (100KB+ for big tables/forms like SalesLine). If you ONLY need relations / FK / DeleteActions / data sources / who-references, call get_relation_graph instead -- it is O(1) and roughly 6x lighter (no source code). Reserve get_object_details for when you genuinely need field details, method bodies, or source code. Also merges live disk source when a custom model path is configured (disk takes priority). Pass `methodName` to get the FULL body of a specific method -- without it, only signatures are returned. Calling twice -- first without methodName to get the full structure and method table, then again with a specific methodName for its full body -- is the CORRECT and INTENDED two-step pattern. Do NOT call a third time for the same object. DISAMBIGUATION: when a name exists as several AOT types (e.g. a Table AND a Form both named 'SalesLine'), this returns the PRIMARY type (Table/Class/Entity before the much heavier Form) and notes the others -- pass `aotType` (e.g. 'AxTable', 'AxForm', or shorthand 'table'/'form'/'class') to pick a specific one. This prevents dumping the heaviest object and truncating the rest. NOT for searching -- use search_d365_code when the name is uncertain. NOT for listing a model's objects -- use list_objects for that.Connector
Matching MCP Servers
- Alicense-qualityAmaintenanceEnables AI assistants to interact with IBM Engineering Lifecycle Management (ELM), including DOORS Next Generation, EWM, and ETM, for managing requirements, work items, tests, and project builds through natural language.MIT
- Alicense-qualityAmaintenanceA federated MCP server that combines IBM's engineering-ai-hub tools with its own authoring and orchestration tools for IBM ELM, enabling AI hosts to manage requirements, models, and compliance through a single interface.MIT
Matching MCP Connectors
Tesouro em Foco is a free remote MCP server that brings Brazilian government bond (Tesouro Direto) pricing into AI assistants such as Claude, Cursor, and any MCP-compatible client. The engine implements the Brazilian National Treasury's official pricing methodology — validated against 269,000+ real trades — and covers all retail bond types: fixed-rate (LTN, NTN-F), inflation-linked (NTN-B Principal, NTN-B), and retirement/education bonds (Renda+ and Educa+, NTN-B1).
Browse and buy ELC Conference 2026 engineering leadership tickets in Prague via AI.
- WHEN: at the START of any release-note / upgrade-impact conversation -- call this BEFORE list_release_note_inputs to check whether a Client Profile already exists for the CURRENT caller's Azure DevOps org/project (auto-detected from DEVOPS_ORG_URL/DEVOPS_PROJECT MCP headers -- you don't pass anything). If found, it gives you the client's currentVersionTag, targetVersionTag, customModelIds (their own extensions AND any attached ISV/vendor models) and the latest diff snapshot in one call -- use those directly as v1/v2/customModelIds for prepare_release_note_context, no further discovery needed. If not found, fall back to list_release_note_inputs and/or save_client_profile.Connector
- Cost a workload with EXACT numbers the caller supplies: arbitrary token counts per request and any monthly volume, not just the 10k/100k/1m presets the other cost tools use. Use this for 'about 800 in and 200 out, 4 million calls a month', or to price one named model across every use-case profile. To compare 2-4 named models like for like at a preset volume, use compare-models-side-by-side instead. Provide a model name to get detailed cost breakdowns, or compare costs across all use case presets. Each figure comes twice: list price, and the optimized price achievable with prompt caching and the batch API. IMPORTANT: Report all cost figures EXACTLY as returned. Do NOT add commentary or recommendations beyond the data.Connector
- USE THIS BEFORE calling `simulate_bond` to discover available bonds, or to disambiguate a user's reference (e.g. 'IPCA+ 2050' → which exact `maturityDate`?). Lists every Tesouro Direto bond currently in the official catalog, grouped by family. Each product includes `launchDate` and `maturityDate`; Renda+/Educa+ also include `conversionDate` and `installments` (240 monthly payments for Renda+, 60 for Educa+). The `year` field meaning depends on family: - prefixado / IPCA+: catalog maturity-year key (e.g. 2031 → maturity in 2031). - Renda+ / Educa+: the **conversion** year shown on the label (e.g. Renda+ 2065 → conversion on 15 Jan 2065, NOT redemption year). Final redemption is ~20 years later for Renda+ and ~5 years later for Educa+. Note: `simulate_bond` accepts bonds outside this catalog too (older maturities for historical simulation) — those calls succeed with a `SYNTHESIZED_BOND` warning in `meta.warnings[]` indicating the product was synthesized. Returns: array of `{ type, label, products: [{ year, maturityDate, launchDate, conversionDate?, installments? }] }`.Connector
- Returns the full published history of a Brazilian reference rate, so you can put macro context next to a bond's own rate history without leaving this server. Rates use the same decimal-fraction convention as every other tool here (`'0.1425'` = 14.25% a.a.), so values compare with `price_history_series` directly, with no unit conversion. Available `indicator` values: - `selic-target` — the **meta Selic** set by the Copom, from the official Banco Central rate history. For `selic-target` this is EVERY decision since the regime began in March 1999, including the meetings that **held** the rate (`outcome: 'hold'`, `changeBps: 0`). Read `outcome` to tell them apart: `up`, `down`, `hold`, or `start` for the single opening entry. Count only `up`/`down` when the user asks how many times the rate actually moved. Two fields are easy to misread. `meetingNumber` is NOT unique: until 2003 a meeting could set a `bias` ('alta'/'baixa') authorizing the Banco Central president to move the target before the next meeting, alone, and those decisions carry `monocratic: true` under the authorizing meeting's number — `effectiveDate` is the key. And `effectiveRate` is the Selic actually realized over the period, a different quantity from the target in `rate`; it is null while a period is still in force. The meta Selic is one of several conditions behind a bond's traded rate; it does not by itself set the rate or price of any Treasury bond, and a move in the same window is not evidence that one caused the other. This is a factual series, not a forecast, a market interpretation, or a recommendation. Returns: `{ series, unit, source: { id, publisher }, items: [{ decisionDate, effectiveDate, rate, previousRate, changeBps, outcome, meetingNumber, extraordinary, monocratic, bias, effectiveRate }] }`, ascending by `effectiveDate`.Connector
- 估算一段文本或指定 token 数在某个大模型上的**输入侧**调用成本,以人民币 ¥ 计价。text_or_tokens 支持两种模式:传自然语言文本时自动估算 token 数(中文按字符、英文按词分别计),传纯数字字符串时直接作为已知 token 数使用。返回:所用估算方法、token 数、按原价计的输入成本;若该模型提供缓存输入价,另给出缓存命中成本、相对原价的节省百分比与倍数差价;末尾附该模型的输入 / 输出 / 缓存输入单价(每百万 tokens)。⚠️ 本工具只计算输入成本,不含输出 token 费用——要估算完整往返成本,需另取输出单价自行相加。Connector
- Ask a DIFFERENT LLM a question and get its answer, billed per token from the Vaaya wallet (model cost + 3%, usually a fraction of a cent). Use it to get a second opinion from a rival model, cross-check an answer, summarize a huge blob cheaply, or query a specific model the user names (Kimi, GPT, Gemini, Claude, DeepSeek, and 300+ more). `model` accepts 'auto' (default: short prompts go cheap, long go mid), 'cheap' | 'mid' | 'best' tiers, or any exact OpenRouter slug like 'moonshotai/kimi-k3'. Typical costs: cheap tier well under 0.1 cents, best tier 1-3 cents per call. Not for the conversation you are already having — it is a one-shot ask to another model.Connector
- FINAL-STEP Leibniz Layer Crypto Commit ($0.01). Writes a trading/agent decision to the append-only Leibniz Layer audit chain and returns a Merkle-proof-style receipt: `tx_hash` (proof of this specific commit), `chain_hash` (the previous commit's hash, linking this one into the chain), and `chain_depth` (this commit's position in the chain). Unlike the evaluate_* tools, this call has no pass/fail verdict of its own — it always succeeds and simply seals the decision. Passing `prior_checks` is optional but recommended: it records which earlier pipeline steps (firewall/wallet/trade/MEV) this specific commit is downstream of, in one auditable record. Always run this LAST, after every other crypto-suite check has passed.Connector
- WHEN: a user encounters an error message, infolog error, or runtime exception in D365. Also handles business-language error explanation when audienceType='business'. Triggers (developer): 'fix this error', 'what causes', 'exception thrown', 'infolog error', 'update conflict', 'outside tts', 'number sequence'. Triggers (business): 'what does this error mean', 'explain this error to me', 'user gets error X', 'que signifie cette erreur', 'message d\'erreur', 'what should the user do when they see this error'. Find known D365 F&O error patterns matching an error message or symptoms description. Matches against a built-in database of common errors (transaction conflicts, security issues, number sequences, posting errors, batch problems, etc.), resolves D365 label IDs from error text (e.g. user sees 'Number sequence not set up' -> finds @SYS70535 -> finds the throwing code), and searches the indexed codebase. Returns root causes, step-by-step resolution, label matches, and source code locations. [~] When the error text contains a D365 label ID (e.g. '@SYS12345'), call `search_labels` first to resolve the label text, then call this tool with the resolved text. Set audienceType='business' for a plain-language explanation targeted at end users instead of developers.Connector
- WHEN: you need a COMPLETE picture of a D365 object in ONE call. Returns in a single response: full structure (fields, method signatures, relation summary) AND all CoC extensions / event handlers -- equivalent to calling get_object_details THEN find_extensions. Use this INSTEAD of those two separate calls to reduce round-trips. Optionally includes best-practice violations (set includeValidation=true). Pass `methodName` to also include the full body of a specific method. Pass `aotType` to disambiguate when several AOT objects share the same name.Connector
- WHEN: you need the COMPLETE bidirectional relation graph for an object in ONE call. Triggers: 'relations of', 'FK of', 'what tables link to', 'quelles tables liées à', 'avant de générer du code', 'before generating code', 'foreign keys', 'delete actions', 'who references', 'qui référence', 'graph de relations'. Returns ALL outgoing edges (FK relations, DeleteActions, DataSources, Extensions, Security...) AND all incoming back-references (forms, entities, CoC classes, privileges... that reference it). Backed by the pre-computed relation index -- O(1) lookup, no vector scan. Much faster and more complete than find_related_objects for known object names. ALWAYS call this before generating code that touches multiple objects or requires join logic. Use find_related_objects when the relation index is not yet built (fallback to vector scan).Connector
- Retrieve the NEXT page of a previously PAGINATED tool output. When a tool result is too large for a single response, it is split losslessly into ordered pages — the footer of each page gives you a `token` and the next `page` number. Call this tool with that token to read the continuation; nothing is dropped, so you can walk every page in order and reconstruct the full result. Pages are cached only briefly (the last few large results). If the token is unknown or expired, re-run the original tool to regenerate it.Connector
- WHEN: you need to know HOW two AOT objects are connected -- the chain of relations linking them. Triggers: 'how is X related to Y', 'comment X est lié à Y', 'path between', 'chemin entre', 'lien entre deux tables', 'connection between', 'is X reachable from Y'. Walks the pre-computed relation graph (FK, DeleteAction, DataSource, Extension, Security edges -- both directions) and returns the SHORTEST navigation path(s) as a chain of object names + edge kinds. Token-light: returns ONLY names and relation kinds, never full object source. O(1)-per-node BFS, no vector scan. Use `get_relation_graph` for the full neighbourhood of a single object; use this to traverse multiple hops between two known objects.Connector
- WHEN: ALWAYS call this FIRST, before prepare_release_note_context -- it discovers the exact D365FO version strings and custom model ids actually indexed on THIS server, which you cannot guess. Triggers: 'release note', 'compare D365 versions', 'upgrade impact for a client', 'what changed for this client', 'regression risk', 'note de version'. Returns every indexed version (exact 'version' string to use as v1/v2, e.g. 10.0.2527.109) and every ready-to-use custom model (exact 'id' to use as customModelIds, plus its name and optional clientGroup tag -- models sharing the same clientGroup belong to the same client and should usually ALL be passed together, e.g. the client's own extensions AND a separate ISV vendor model). IMPORTANT: this server holds the ACTUAL indexed code diff and the client's ACTUAL custom code -- generic Microsoft Learn / Azure Updates / documentation-search tools do NOT have this data and must NOT be used for D365 F&O release-note or upgrade-impact questions about a specific client; those tools only know public, generic release notes, not this client's real regression/opportunity picture.Connector
- Run up to 100 record writes in ONE call (contact/company/deal/activity) - the fast path for imports/migrations. operations: [{object, method:create|update|delete, data|patch, id?}]. Returns a per-op result array (partial success). Every op still counts against your quota (batch saves round-trips, not quota).Connector