Skip to main content
Glama
Sign In

Selenios

by com.selenios.back
OverviewDiscussionsAdmin

List interviews by date

list_meetings
Read-onlyIdempotent

List the interviews and meetings scheduled in a date range, internal meetings included, optionally only those whose title contains given words (e.g. "the Check Point meeting on October 21", "which interviews did I have yesterday?"). Returns title, status, date and time, candidate, and whether a transcript and a report exist, oldest first. total counts every interview in the range; truncated: true means not all of them were returned and a narrower range or title returns the rest. It does not search what was said in the interviews.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the range, inclusive (ISO 8601; a bare date includes that whole day)
fromYesStart of the range, inclusive (ISO 8601 date or datetime)
titleNoOnly interviews whose title contains every one of these words, in any order (case- and accent-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description only needs extra behavior, and it delivers: sort order ('oldest first'), the returned fields, and the pagination contract (`total` counts all, `truncated: true` means narrow the range or title). That truncation-to-remedy mapping is the kind of detail an agent must have to recover from a partial result.

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?

Scope comes first, then filter behavior, then return shape, then pagination caveat, then the exclusion. Every sentence carries distinct information and nothing repeated from the schema or annotations.

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?

With no output schema, the description correctly spends words on return fields and the `total`/`truncated` semantics, and it closes the boundary against transcript search. For a 3-parameter read tool this is sufficient to call correctly and interpret results.

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 baseline would be 3; the description earns an extra point by showing how real questions map onto `title` (word containment, any order) and by tying the date range to the truncation remedy. It adds no ISO-8601 syntax detail, but the schema already carries that.

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 ('List the interviews and meetings scheduled in a date range'), states the internal-meetings inclusion rule, and names the title filter. It ends by explicitly disclaiming content search, which cleanly separates it from search_meeting_transcripts.

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?

Usage is well framed with natural-language example queries ('the Check Point meeting on October 21', 'which interviews did I have yesterday?') and an explicit exclusion ('does not search what was said'). The gap is that sibling scoped listers like list_candidate_meetings and list_job_meetings are never mentioned, so an agent filtering by candidate or job has no steering here.

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

All Selenios toolsInspect
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