Skip to main content
Glama

Get a conference and its abstracts

get_conference
Read-onlyIdempotent

Use this when the user asks about one meeting from list_conferences, or what was presented there: its organizer, site and editions; with edition, that edition's abstracts most worth reading, each with the paper it was later published as. An abstract is not a peer-reviewed paper.

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": {
      "id": "<id>"
    },
    "name": "get_conference"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConference id from list_conferences, e.g. gsa.
limitNoResults per page.
cursorNoFrom the last page's `pagination.next_cursor`; keep the other arguments the same.
editionNoAn edition from `editions`, e.g. 2025: list its abstracts.
min_visibilityNoWith `edition`: which abstracts to list, from the most to the least worth reading: `core`, `visible`, `searchable`, `matchable`, `out`. Default `visible`, those worth reading.visible

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from `pagination.next_cursor` of the previous page. Keep the other parameters the same."New value: +"From the last page's `pagination.next_cursor`; keep the other arguments the same."
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page, 1 to 25."New value: +"Results per page."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds two useful things beyond that: the two operating modes (with and without `edition`) and the caveat that an abstract is not a peer-reviewed paper. It says nothing about pagination behavior or result ordering, keeping it at a solid but not rich level.

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?

Front-loaded with the usage trigger and no filler sentences; the closing caveat about abstracts earns its place. The main sentence is long and semicolon-chained, making it slightly harder to parse than it needs to be.

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 5-parameter read-only tool with annotations covering safety and no output schema, the description covers modes, return content and a semantic caveat. It omits any mention of pagination or how the two modes interact with `limit`/`cursor`, though the schema documents those fields directly.

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 earns an extra point by explaining the mode switch: `edition` turns the call into an abstract listing and couples with `min_visibility`. That conditional relationship is the one thing the schema fields alone don't make obvious.

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?

Specific verb (get) plus resource (a conference) with an explicit statement of what is returned: organizer, site and editions, and with `edition` that edition's abstracts plus the paper each was published as. It distinguishes itself from the sibling list_conferences by naming it as the source of the id.

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?

Gives a clear trigger: the user asks about one meeting from list_conferences or what was presented there. It names the sibling that supplies the id but never explicitly states when to prefer list_conferences over this tool, so the exclusion is left to inference.

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