Skip to main content
Glama

List asks with candidates

listAsks
Read-onlyIdempotent

List the questions between your company and candidates in your interview processes, newest first: the ones your team asked through askCandidate, and the ones a candidate's agent asked your company. Each shows who asked, what, its status (open, resolved, dismissed, expired) and, once closed, the outcome. An open ask your team asked is still waiting on the candidate's side.

askId is a tool input for dismissAsk only; refer to asks by candidate and question. Returns one page at a time; when hasMore is true, pass nextCursor as cursor.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of asks to return (max 50).
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
cursorNoPass nextCursor from a previous call to get the next page.
statusNoOnly asks in this status. Omit for all.

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description adds ordering ('newest first'), the four status values, the presence of an outcome once closed, and pagination mechanics (hasMore → nextCursor). It also discloses that inputs and results are privately recorded for usage tracking, which is real behavioral context an agent cannot get from annotations. Minor gaps remain: no indication of result volume expectations beyond the page note, and no mention of permission requirements.

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?

The core listing statement and the two-direction definition are front-loaded, followed by pagination and then a compliance note; every sentence carries information. It is slightly dense in the middle paragraph, where the askId/dismissAsk aside interrupts the pagination guidance, but nothing is wasted.

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?

An output schema exists, so return shape need not be described, and the description still covers ordering, status vocabulary, outcome fields and paging. Combined with full schema coverage of four parameters and a complete annotation set, an agent has what it needs to call this correctly; only explicit when-to-use routing is thin.

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?

Schema description coverage is 100%, so limit, orgId, cursor and the status enum are already documented in structured form. The description reinforces the cursor contract ('when hasMore is true, pass nextCursor as cursor') and clarifies that askId is not a parameter here, but adds no new semantics for limit or orgId. 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?

States a specific verb and resource ('List the questions between your company and candidates in your interview processes') and goes further by defining both directions of the resource: asks the team issued via askCandidate and asks a candidate's agent issued to the company. That definition lets an agent distinguish this list tool from single-purpose siblings like askCandidate or dismissAsk without opening the schema.

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?

Usage context is implied rather than stated: the description explains what 'open' means for a team-issued ask ('still waiting on the candidate's side') and warns that askId is only an input for dismissAsk, which usefully deflects a wrong-tool call. However, it never says when to reach for this tool versus alternatives, nor does it give a concrete trigger such as 'use when you need to check unanswered questions before following up'.

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.

Resources