misim-tax-research
Server Details
Israeli tax research: source-grounded answers with official citations, in Hebrew.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly described.
The single tool uses snake_case naming, which is consistent with itself. There is no inconsistency.
A single tool for Israeli tax research feels thin; while it may be functional, a toolset of 1 is considered borderline according to the calibration guidelines.
The tool provides a comprehensive search over official sources, but lacks separate operations for browsing or filtering specific document types, leading to notable gaps.
Available Tools
1 toolmisim_tax_searchAInspect
Israeli tax-law research engine, source-grounded. Returns an answer anchored ONLY in official sources (primary legislation, regulations, case law, tax rulings, circulars, VAT, national insurance), with citations, a certainty level, and a disclaimer. Israeli law only. Abstains honestly when no sufficient source exists — never fabricates. מנוע מחקר מס ישראלי מבוסס-מקורות רשמיים.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The tax question, preferably in Hebrew. Israeli law only. שאלת המס (דין ישראלי בלבד). | |
| max_sources | No | Max number of live-web sources to attach (default 3). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully bears the burden. It discloses that answers are based solely on official sources, include citations, certainty level, and disclaimer, and that the tool abstains rather than fabricates. No contradictions or omissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, front-loaded with the core purpose, and contains no extraneous information. The bilingual addition is a minor, contextually appropriate extension. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple parameter set and lack of output schema, the description sufficiently explains the return structure (citations, certainty, disclaimer) and key behavior (abstention). It is complete for an AI agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% as both parameters have descriptions. The main description reinforces the 'Israeli law only' constraint but adds no extra semantic value beyond what the schema already provides, meriting the baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool is an 'Israeli tax-law research engine' that returns answers anchored only in official sources, with clear verb and resource. No siblings exist, so differentiation is not required, but the purpose is unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates the tool is for Israeli tax law queries only and honestly abstains when no sufficient source exists. While there are no alternatives to compare, the context is well defined, but explicit 'when not to use' guidance is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!