Skip to main content
Glama

The Valley Desk

Search the research directory

search
Read-onlyIdempotent

Search The Valley Desk directory of research software, publications and clinical studies connected to the nine-county Delaware Valley (Philadelphia region). Matches titles, topics, institutions and keywords. Every filter is optional. Returns up to 24 records per page with the site URL, the Verified or Listed evidence label and labelled dates.

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

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to software projects, publications or clinical studies.
pageNoPage number. Each page holds up to 24 records.
sortNoadded: newest directory additions first (default). date: newest published or pushed first. title: A to Z.
labelNoLimit to one regional evidence label.
queryNoWords to match, for example "sepsis prediction".
topicNoTopic name, for example "Medical imaging". list_topics_and_counties returns the names.
countyNoOne of the nine Delaware Valley counties.
date_toNoLatest published date or last code push. YYYY, YYYY-MM or YYYY-MM-DD.
added_toNoLatest date added to the directory. YYYY, YYYY-MM or YYYY-MM-DD.
date_fromNoEarliest publication, last code push or study registry update date. YYYY, YYYY-MM or YYYY-MM-DD.
added_fromNoEarliest date added to the directory. YYYY, YYYY-MM or YYYY-MM-DD.
institutionNoInstitution name or id, for example "Drexel University". list_institutions returns the names.

Output Schema

NameRequiredDescriptionDefault
pageYes
resultsYes
page_sizeYes
truncatedNoTrue when records were dropped to fit the response size cap.
browse_urlNoThe same search on the site.
total_pagesYes
total_recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds real behavior beyond that: 24 records per page pagination and the shape of returned evidence (site URL, Verified or Listed label, labelled dates). It does not state how multiple filters combine, which is the main remaining operational unknown.

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?

Front-loaded with the verb and corpus, then matching behavior, then optionality, then return shape — every sentence carries information with no filler or repetition of 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 twelve-filter read-only search with a full schema and an output schema, the description covers purpose, matching, optionality, pagination, and return contents. The one gap is filter-combination semantics (AND vs OR, empty-query behavior), which matters at this parameter count.

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 baseline is 3, but the description adds meaning the schema does not: the query matches titles, topics, institutions, and keywords, clarifying what free-text actually searches against. It also signals that all twelve filters are optional, which is only derivable from the schema by inspecting required fields.

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 resource with scope: searching a directory of research software, publications, and clinical studies across nine Delaware Valley counties, and what fields are matched. An agent can tell what it retrieves, but the description never contrasts it with siblings like whats_new or fetch, so sibling differentiation is left implicit.

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?

"Every filter is optional" gives useful implied guidance that a bare query returns the full directory, but there is no explicit statement of when to choose this over whats_new or fetch, nor any when-not guidance. Usage is inferable rather than stated.

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.