Skip to main content
Glama

About Datari Labs

about_datari
Read-onlyIdempotent

Explains what Datari Labs is, how its free data-referral service works, which companies fit, and how it works. Use this when someone asks whether they can sell or license their company's data, or who buys company data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this as a safe, read-only, idempotent, closed-world, non-destructive operation, so the safety picture is fully covered. The description adds only that the content is explanatory background about the service. It doesn't say whether the answer is self-contained or whether the agent should hand off to check_fit or register_company afterward.

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?

The usage trigger is front-loaded in the second sentence, which is well-structured. However, the opening sentence is redundant: 'how its free data-referral service works ... and how it works' says the same thing twice and costs clarity.

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

Completeness3/5

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

For a simple zero-argument informational tool with no output schema, the description covers what it explains and when to invoke it. It leaves open whether a typical flow continues into check_fit or register_company, which is the one piece of guidance an agent calling this tool in a sequence would benefit from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is fully specified with additionalProperties false, so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool applies, and the description correctly implies no arguments are needed.

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 states a specific verb ('Explains') and a clear subject (what Datari Labs is, its free data-referral service, and eligibility), so an agent knows this is an informational tool. It stops short of 5 because 'which companies fit' overlaps conceptually with the sibling check_fit, and the phrase 'and how it works' restates the earlier clause rather than adding a distinct facet.

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?

It gives an explicit trigger condition: use it when someone asks whether they can sell or license their company's data, or who buys company data. That is a concrete context an agent can match on. It stops short of naming exclusions or pointing to check_fit or register_company for the follow-up steps, which would make routing unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources