Versium REACH

Docs Search Mcp Tool

docs_search

Read-onlyIdempotent

Search Versium's official documentation for information about the web application or APIs.
Use this tool when a user has questions about how to use the Versium REACH platform.

**Usage Tips:**
- Use `docs_target: app` for questions about the Versium REACH web application
- Use `docs_target: api` for questions about Versium's data enrichment APIs
- Use `docs_target: both` (default) to search all documentation

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return per documentation source
`query`	Yes	The search query to find relevant documentation
`docs_target`	No	Which documentation to search: "app" for web application docs, "api" for API docs, or "both"	both

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not restate safety traits. The description adds useful contextual scope about searching official docs and defaulting to both doc sources. However, it does not add deeper behavioral detail such as response shape, pagination, or source behavior beyond the schema.

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?

The description is concise and well-structured: a clear purpose sentence, a usage context sentence, and three bullet usage tips. Every line adds practical value without irrelevant filler.

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, fully detailed annotations, and only one required parameter, the description does enough by stating the search domain and when to use the tool. It could be slightly more complete with explicit mention that search is read-only, but the annotations already provide that context.

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 input schema has 100% parameter coverage with descriptions and defaults. The description adds extra semantic value by explaining the meaning of 'app' vs 'api' docs_target choices in practical terms. This goes beyond the schema's basic enum documentation.

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?

The description clearly identifies the tool's function: searching Versium's official documentation for web application or API information. This is specific and aligned with the tool name, and it is clearly distinct from all sibling tools, which handle data append, job, project, and list operations rather than documentation search.

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?

The description explicitly states when to use the tool: 'Use this tool when a user has questions about how to use the Versium REACH platform.' It also provides concrete guidance for choosing docs_target values. It does not explicitly discuss alternatives or when not to use the tool, but the sibling context makes alternative use cases obvious.

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

All Versium REACH tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: list generation (B2B vs B2C), enrichment (contact, demographic, firmographic, C2B, IP-to-domain), project/list management, job lifecycle, and validation. No two tools appear to do the same thing, so an agent can reliably select the correct one.

Naming Consistency5/5

All tool names follow the verb_noun pattern consistently, using verbs like list, show, create, preview, search, validate, append, and estimate. Even the segmented append tools (c2b_append, contact_append, demographic_append, firmographic_append, ip_to_domain_append) follow the same pattern with clear noun modifiers. No mixed conventions or vague verbs.

Tool Count4/5

With 19 tools, this is on the higher side but still well-scoped for a data enrichment and list-building platform. The count covers distinct functional areas (audience estimation, enrichment, job/project management, list inspection, documentation) without unnecessary bloat. It feels slightly heavy but each tool earns its place.

Completeness4/5

The tool surface covers the core workflows: estimating audiences, creating and monitoring jobs, managing projects and lists, and enriching records with various data types. Minor gaps exist, such as no explicit delete/update operations for projects or lists, and no direct file download for list contents (though preview_list and show_list provide partial coverage). These are non-blocking gaps that agents can work around.

Resources

Need Help?