Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tealfabric/claude-mcp-tealfabric --skill mcp-tool-call-efficiencygit clone --depth 1 https://github.com/tealfabric/claude-mcp-tealfabricWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tealfabric/claude-mcp-tealfabric/mcp-tool-call-efficiency)<a href="https://agentmods.dev/skills/tealfabric/claude-mcp-tealfabric/mcp-tool-call-efficiency"><img src="https://agentmods.dev/badge/skills/tealfabric/claude-mcp-tealfabric/mcp-tool-call-efficiency/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tealfabric/claude-mcp-tealfabric/mcp-tool-call-efficiency"><img src="https://agentmods.dev/badge/skills/tealfabric/claude-mcp-tealfabric/mcp-tool-call-efficiency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00023 | $0.00760 |
| Opus 5.5 | $0.00009 | $0.00304 |
| Sonnet 5.5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
Tealfabric MCP Tool Call Efficiency scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- Tealfabric MCP Tool Call Efficiency — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tealfabric MCP Tool Call Efficiency
Use this skill when you need reliable MCP calls with minimal retries.
Objective
- Minimize trial-and-error with tool schemas.
- Use short call sequences that return actionable data quickly.
- Prefer deterministic payloads and avoid over-supplying fields.
Core Rules
- Start with a list tool before create/update unless the user already gave exact IDs.
- Send only required fields first; add optional fields in follow-up updates.
- Keep payload keys exactly aligned to tool schema names.
- For enum-like fields, reuse known values from docs/examples.
- If a call fails, fix one parameter at a time (do not rewrite whole payload blindly).
Fast Paths
Connectors: find and validate
tealfabric_list_connectorswith empty input.- If connector identified, call
tealfabric_get_connector_oauth2_required. - Call
tealfabric_test_connectorwithconnector_idand optionalconfiguration.
{
"tool": "tealfabric_test_connector",
"args": {
"connector_id": "YOUR_CONNECTOR_ID",
"configuration": {}
}
}
Integrations: create with minimum risk
tealfabric_list_integrationsto avoid duplicates.tealfabric_create_integrationwith required fields only (name,type).tealfabric_update_integrationfor optional metadata once ID is confirmed.
{
"tool": "tealfabric_create_integration",
"args": {
"name": "Salesforce Sync",
"type": "api"
}
}
Webapps: create then publish
- Ensure a
webapp_userexists; never usetenant_adminaswebapp_user_id. tealfabric_create_webappwith requiredname,type,page_content,webapp_user_id.- Edit with
tealfabric_update_webapportealfabric_create_webapp_versionas needed. tealfabric_publish_webappwith bothwebapp_idandversion.
{
"tool": "tealfabric_publish_webapp",
"args": {
"webapp_id": "YOUR_WEBAPP_ID",
"version": 1
}
}
Documents: text vs binary
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · -3 lines da3974a2b466
- 2mo ago First seen · 103 lines · 23 tokens per session scan A 9088f2e8dfa6
Tealfabric MCP Tool Call Efficiency is a skill published in the GitHub repository tealfabric/claude-mcp-tealfabric (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 760 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…