Ysaere

Sourced Brief

sourced_brief

Sourced Brief. Starts a short cited memo and returns a run_id right away. Call check_report_status with that run_id until status is completed. Costs 3 credits after a usable memo. Informational only — not verified fact.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "sourced_brief"
  }
}

Input Schema

Name	Required	Description
`focus`	No	Optional angle (e.g. distribution risk).
`target`	Yes	Company, deal, property, or market category to research.
`context`	No	Optional caller context.
`sources`	No	Default ["web"]. Include "vault" for tenant file chunks.
`file_ids`	No	Optional Vault file scope when sources includes vault.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Adds real value beyond the annotations: async start, cost of 3 credits charged only after a usable memo, and an "informational only — not verified fact" caveat. That is useful, but it omits what happens on failure or whether re-invocation charges twice, which matters for a non-idempotent, metered operation. Score 3 rather than higher because the billing and failure semantics remain ambiguous.

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?

Four short sentences, front-loaded with the artifact and the run_id return, then the follow-up step, the cost, and the disclaimer. The only waste is the opening "Sourced Brief." which merely restates the title.

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?

For a five-parameter async job with full schema coverage and no output schema, the definition covers the return contract (run_id), the next step, cost, and reliability caveat. It stops short of describing what the memo contains or failure/retry behavior, which keeps it from a 5.

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?

Schema coverage is 100%, so the schema already documents all five parameters, and the description adds no parameter details of its own. The baseline for full coverage is a 3, but the description does explain the target's purpose contextually through the memo concept, so a 4 is warranted.

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?

States a specific verb and artifact: "Starts a short cited memo and returns a run_id right away." That is concrete enough to tell it apart from status-checking siblings, but it never distinguishes itself from the similar-sounding quick_brief or the deeper intelligence tools in the catalog.

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

Usage Guidelines3/5

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

It gives a clear follow-up workflow ("Call check_report_status with that run_id until status is completed"), which is genuine procedural guidance. However, it offers no conditions for choosing this over sibling briefs such as quick_brief or the deeper intelligence tools, so selection guidance is only implied.

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

All Ysaere 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?