Dayze — Life Context

Search MCP Tools

search_tools

Read-only

Discover Dayze MCP tools outside the core default expert listing. Returns matching opt-in tools with their toolset and how to enable them (URL ?toolsets=, tools/list params, or tools.* connection scopes). Call with no query to list available toolsets. Core everyday tools are already listed; this does not replace tools/list. ($0.00)

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

Input Schema

Name	Required	Description
`limit`	No	Max tools to return (1–50, default 20).
`query`	No	Case-insensitive match against tool name, title or description. Empty lists toolsets.
`toolset`	No	Limit to one opt-in pack id (inventory, finance, crm, …) or "all" for every extra.
`include_core`	No	When true, also return matches from the default core set. Default false.

Output Schema

Name	Required	Description
`note`	Yes
`query`	No
`tools`	Yes
`toolset`	No
`toolsets`	Yes
`enable_all`	Yes	How to restore the full expert catalog for this connection.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious context beyond that: results carry the owning toolset plus the three enablement mechanisms (URL ?toolsets=, tools/list params, tools.* scopes) and a $0.00 cost signal. It stops short of describing result shape, but the output schema covers that.

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?

Five short sentences, each front-loading the most decision-relevant fact: purpose first, then return content, then the no-arg behavior, then the exclusion. The trailing '($0.00)' is terse but informative; nothing is padded or repeated.

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 annotations, a fully described 4-parameter schema and an output schema, the description's job is narrow and largely met — it explains enablement paths and the core-vs-opt-in boundary. Minor gap: it doesn't say what happens when a query matches nothing or how results are ordered, though the output schema may cover the shape.

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 limit, query, toolset and include_core are already documented with enum-like guidance. The description's only parameter-adjacent content is the empty-query behavior, which the schema already states ('Empty lists toolsets'), so it adds little beyond the baseline.

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 opens with a specific verb and resource ('Discover Dayze MCP tools') and immediately scopes it to tools 'outside the core default expert listing.' It further distinguishes itself from tools/list, so an agent can tell exactly what this call returns versus the core catalog.

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?

It states when to reach for this tool (opt-in tools not in the default listing), gives the no-argument behavior ('Call with no query to list available toolsets'), and explicitly rules out a wrong use case ('this does not replace tools/list'). Alternatives and exclusions are both present.

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

All Dayze — Life Context 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.