Taseli

Results this month

get_results

Read-onlyIdempotent

How the whole business is doing, exactly as Home shows it: Home's verdict sentence first, then results in the business's own word (leads, sales, calls…) over the last 28 full days against the 28 before, the cost per result, this month's spend against the budget, results per week, and which campaigns work best and least (over their last 30 days).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_results"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Answer language. The business's language by default.

Output Schema

Name	Required	Description
`best`	No	Campaigns over their synced last 30 days (campaigns have no daily rows).
`note`	No	A plain note instead of data (nothing connected yet, not available here).
`sales`	No
`scope`	No	Always the whole business, all accounts together.
`spent`	No
`weeks`	No
`worst`	No
`budget`	No
`window`	No	The days `results` covers (ending yesterday, Israel's day) and the days before.
`results`	No	Results (the business's own result word, `resultWord`) in the last 28 full days, the window Home shows.
`verdict`	No
`currency`	No
`forecast`	No
`budgetSet`	No
`truncated`	No
`overBudget`	No
`resultWord`	No	What one result is for this business, plural, in the answer language (leads, sales, calls…).
`resultsKnown`	No	False when the 28 days have no results, so there is no cost per result.
`costPerResult`	No
`resultsBefore`	No	The 28 days before.
`truncatedNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 6, 2026

addedOutput schema / properties / costPerResult / anyOf

Added value: +[
+  {
+    "description": "Over the same 28 days, in `currency`; null with no results (never read as 0).",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / costPerResult / description

Removed value: -"Over the same 28 days, in `currency`; 0 with no results."

removedOutput schema / properties / costPerResult / type
```
Removed value: -"number"
```

addedOutput schema / properties / resultsKnown

Added value: +{
+  "description": "False when the 28 days have no results, so there is no cost per result.",
+  "type": "boolean"
+}

First observedNov 3, 2026

TDQS

B3.4/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 closed-world, so safety is covered; the description adds real behavioral detail beyond them, namely the exact comparison windows (28 full days vs. the prior 28, campaigns over their last 30 days) and the fixed ordering with the verdict sentence first. It does not discuss whether data can be empty or how fresh it is, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one sentence, front-loaded with the core purpose, and every clause carries content information. However, the sentence is very long with stacked parentheticals and filler phrases like 'in the business's own word', which make it slower to parse than a short lead plus a bulleted content list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to document return shapes and instead focuses on which metrics appear and over what periods, which is the right division of labor. For a zero-required-parameter read tool with rich annotations, the only notable omission is disambiguation from adjacent review/benchmark tools.

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 description coverage is 100% and the single parameter is an enum with a documented default ('The business's language by default'). The description adds nothing about the language parameter, so this sits at the baseline of 3 where the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description concretely enumerates what is returned: a verdict sentence, results in the business's own units over the last 28 full days vs. the prior 28, cost per result, spend vs. budget, weekly results, and best/worst campaigns. That is far more specific than the title 'Results this month'. It stops short of 5 because it never names or contrasts a sibling (e.g. get_account_review, get_business, get_benchmarks), which an agent must still disambiguate on its own.

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

Usage Guidelines2/5

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

There is no 'use this when' guidance, no exclusions, and no mention of alternatives, despite several overlapping siblings such as get_account_review, get_business, and get_benchmarks. The only implicit signal is 'exactly as Home shows it', which hints at a general snapshot but does not tell an agent when to prefer another tool.

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

All Taseli tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?