phasefolio

get_evidence

Read-onlyIdempotent

Fetch the evidence register entries for a scenario — the citations, sources, and supporting documents the analyst attached to back the assumptions. Use this when an analysis question references 'what's the evidence for X?'

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scenario_id`	Yes	UUID of the scenario whose evidence register entries to fetch.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Array of evidence-register entries. Each entry has fields like assumption_path, source_url, source_date, excerpt, freshness, confidence — see /methodology/evidence-standards for the canonical schema.

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, repeatable read. The description's 'Fetch' wording aligns without contradiction, but it adds no behavioral detail beyond what annotations already cover.

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 zero filler. The first sentence states the action and object, the second gives a practical usage cue. Information is front-loaded and every sentence earns its place.

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

Completeness5/5

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

For a single-parameter read tool with an output schema and strong safety annotations, the description fully covers what is fetched, what content is included, and when to invoke it. Nothing critical 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?

The input schema fully describes scenario_id, including UUID format and a description matching the tool's purpose. Since schema description coverage is 100%, the description adds no new parameter-level meaning, so baseline 3 is appropriate.

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: 'Fetch the evidence register entries for a scenario.' It further defines what is included ('citations, sources, and supporting documents'), distinguishing it from sibling tools like get_scenario or get_dossier.

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?

Provides an explicit usage trigger: 'Use this when an analysis question references "what's the evidence for X?"'. It does not explicitly mention excluded cases or alternatives, but the context for when to call it is clear.

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

All phasefolio 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.4/5.0

Disambiguation5/5

Each tool targets a distinct entity or operation: get_* fetches specific objects, query_* searches datasets, list_scenarios enumerates, while triage_asset and verify_export are standalone actions. There is no functional overlap or ambiguity among the 13 tools.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in lowercase with underscores. The verbs (get, list, query, triage, verify) clearly indicate the action, and nouns identify the target. This uniform scheme makes the tool purpose predictable.

Tool Count5/5

With 13 tools, the server is well-scoped within the ideal 3–15 range. Each tool addresses a specific aspect of the drug-development analysis domain (project/scenario context, evidence, methodology, benchmarks, risk, landscape, SEC deals, dossier, verification, triage) without redundancy.

Completeness4/5

The read-side surface is thorough for the domain: projects, scenarios, evidence, methodology, benchmarks, drug risk, landscape, SEC deals, dossier, export verification, and triage are all covered. The only minor gap is the lack of a list_projects tool, but get_project can fetch a known project, providing a workaround.

Resources

Need Help?