Datailo: one MCP connection to tenders, EU regulation and law

Invoke a child tool

datailo_invoke

Sign-in required: call datailo_connect(email) and datailo_connect_verify first (free, one email) unless this connection is already signed in. Call one tool of an enabled service through the hub: service, tool name and its arguments (see datailo_tool_schema). Returns the service's own result.

Input Schema

Name	Required	Description
`args`	No
`tool`	Yes
`service`	Yes
`session`	No	The `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / session / description

Previous value: -"The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."New value: +"The `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / session

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.",
+  "title": "Session"
+}

First observedSep 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description usefully adds the authentication requirement and the fact that the service's own result is returned unchanged. It does not warn that a child tool may be destructive or that failures surface as the child's errors, so it is strong but not fully exhaustive.

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

Conciseness5/5

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

Two sentences with no filler. The blocking prerequisite (sign-in) is front-loaded before the functional description, which is the correct priority order for an agent that must clear auth before calling.

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 covers the gap minimally with 'Returns the service's own result'; auth and sibling discovery are covered. Error behavior and how to discover which services are enabled are left implicit, but nothing essential for a correct call is missing.

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 only 25% (only `session` is documented), so the description has to carry the load. It identifies service, tool name and arguments, and points to datailo_tool_schema for the passthrough `args` shape, but adds no format, naming convention, or validation detail beyond restating the field names.

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?

States a specific verb and resource: it calls exactly one tool of an enabled service through the hub, taking service, tool name and arguments. It also names the sibling that explains the argument shape (datailo_tool_schema), so the agent can distinguish it from connection and catalog tools without opening a schema.

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

Usage Guidelines5/5

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

Gives the prerequisite flow explicitly (call datailo_connect(email) then datailo_connect_verify first), states the exception (unless already signed in), and routes the agent to datailo_tool_schema for the child tool's argument contract. The when-to-use condition and the alternative are both spelled out.

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

All Datailo: one MCP connection to tenders, EU regulation and law 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?