Skip to main content
Glama

The Valley Desk

New listings since a date

whats_new
Read-onlyIdempotent

List records added to The Valley Desk directory on or after a date, newest additions first. The date is when the record entered the directory, which can differ from when the research was published.

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": {
      "since": "<since>"
    },
    "name": "whats_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit to software projects, publications or clinical studies.
pageNoPage number. Each page holds up to 24 records.
sinceYesEarliest date added, as YYYY-MM-DD.
topicNoTopic name, for example "Medical imaging". list_topics_and_counties returns the names.
countyNoOne of the nine Delaware Valley counties.
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.7/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds useful behavior beyond annotations by specifying newest-first ordering and explaining that 'since' refers to directory-entry date rather than research publication date.

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 two efficient sentences with the main purpose front-loaded. The second sentence earns its place by clarifying a subtle date semantic that affects correct use.

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?

The description is complete for a filtered listing tool with rich schema and output schema support. Its main gap is the absence of sibling routing guidance, which would help an agent choose it over search or fetch.

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 description coverage is 100%, so the schema already documents the parameters. The description adds meaningful semantic detail for the required 'since' parameter by clarifying that it tracks when the record entered the directory, which can differ from publication date.

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?

The description states a specific verb and resource: 'List records added to The Valley Desk directory on or after a date, newest additions first.' This is clear, but it does not explicitly distinguish the tool from siblings such as search or fetch.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance or alternatives. It implies the tool is for newly added records, but never says when to choose it over search or fetch.

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.