ATI Lab

Get ATI Lab's published results

atilab_get_published_results

Read-onlyIdempotent

Returns results from ATI Lab's own production systems (e.g. shipment intake from email: 95% less manual work), each as published on atilab.io, with the source page. Optional query filters by words in the system or outcome. Industry pages on atilab.io also show third-party results from other companies; those are not ATI Lab clients and are not returned here.

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": "atilab_get_published_results"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Optional filter, e.g. "support" or "email".
`intent`	No	Optional: the user's goal in a few words, e.g. "shortlist AI partners for an insurance broker". No names, emails or other personal details. ATI Lab uses it to improve these tools.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / intent

Added value: +{
+  "description": "Optional: the user's goal in a few words, e.g. \"shortlist AI partners for an insurance broker\". No names, emails or other personal details. ATI Lab uses it to improve these tools.",
+  "type": "string"
+}

First observedOct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: results are sourced from atilab.io pages and returned with their source page, and results from other companies are filtered out – useful expectations about the returned set. No rate limits or pagination are mentioned.

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

Conciseness4/5

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

Front-loaded with what is returned, followed by filter behaviour and the exclusion clause; each sentence earns its place. It is slightly dense for a two-optional-parameter read tool but not padded.

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?

No output schema exists, and the description compensates by describing what a result contains (a result plus its source page). With annotations covering safety and full schema coverage on params, the definition is complete enough to call correctly; only return shape/volume details are absent.

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 coverage is 100%, so both parameters are already documented, including the privacy caveat and telemetry purpose of `intent`. The description restates the word-filter behaviour of `query` ('filters by words in the system or outcome') which sharpens what is matched, but adds little the schema does not already carry.

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

Purpose5/5

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

Specific verb+resource: returns results from ATI Lab's own production systems, each with the source page. It explicitly carves out what is NOT included (third-party results shown on industry pages), which lets an agent separate this from a generic site search without opening the schema.

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

Usage Guidelines4/5

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

States the optional query usage and the exclusion condition (non-ATI-Lab third-party results are not returned), which is clear context for when this is the right tool. It does not name a sibling alternative (e.g. atilab_get_page) for cases where the user wants third-party results, so it stops short of explicit routing.

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

All ATI Lab 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?