Skip to main content
Glama

Get event details

fetch
Read-onlyIdempotent

Get the public facts of one event by its id from search: dates, location, public deadlines, official and source URLs, and the public calendar feeds that contain it.

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

Input Schema

NameRequiredDescriptionDefault
idYesEvent id from search.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesResearchCal event page.
textYesPlain-text summary of the event facts.
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedOutput schema / $defs / DeadlineInfo / properties / deadline_type
      Added value: +{
      +  "description": "full_paper, extended_abstract, abstract, panel_proposal, call_for_works, application, registration, notification (a decision date), or empty when not yet typed.",
      +  "title": "Deadline Type",
      +  "type": "string"
      +}
    • addedOutput schema / $defs / DeadlineInfo / properties / open_call
      Added value: +{
      +  "description": "True when the deadline is open and asks for a submission or an application. Registration, decision and untyped deadlines are never open calls.",
      +  "title": "Open Call",
      +  "type": "boolean"
      +}
    • changedOutput schema / $defs / DeadlineInfo / required
      Previous value: -[
      -  "label",
      -  "kind",
      -  "date",
      -  "time",
      -  "timezone",
      -  "status",
      -  "url"
      -]New value: +[
      +  "label",
      +  "kind",
      +  "date",
      +  "time",
      +  "timezone",
      +  "status",
      +  "deadline_type",
      +  "open_call",
      +  "url"
      +]
    • addedOutput schema / $defs / DetailFact
      Added value: +{
      +  "properties": {
      +    "kind": {
      +      "description": "Eligibility: career_stage, membership, affiliation, group, region, nomination or unpublished_only. Submission: format, length, method, document or template.",
      +      "title": "Kind",
      +      "type": "string"
      +    },
      +    "text": {
      +      "title": "Text",
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "Official page that states it.",
      +      "title": "Url",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "text",
      +    "url"
      +  ],
      +  "title": "DetailFact",
      +  "type": "object"
      +}
    • addedOutput schema / $defs / EventMetadata / properties / eligibility
      Added value: +{
      +  "description": "Each restriction on who may submit, with its source.",
      +  "items": {
      +    "$ref": "#/$defs/DetailFact"
      +  },
      +  "title": "Eligibility",
      +  "type": "array"
      +}
    • addedOutput schema / $defs / EventMetadata / properties / submission
      Added value: +{
      +  "description": "How to submit: format, length, method, documents, template.",
      +  "items": {
      +    "$ref": "#/$defs/DetailFact"
      +  },
      +  "title": "Submission",
      +  "type": "array"
      +}
    • addedOutput schema / $defs / EventMetadata / properties / submission_checked_on
      Added value: +{
      +  "description": "Date (ISO) of the check of how to submit, or empty.",
      +  "title": "Submission Checked On",
      +  "type": "string"
      +}
    • addedOutput schema / $defs / EventMetadata / properties / submission_ready
      Added value: +{
      +  "description": "True when the deadline, its type, the submission method and who may submit are all checked.",
      +  "title": "Submission Ready",
      +  "type": "boolean"
      +}
    • addedOutput schema / $defs / EventMetadata / properties / who_may_submit
      Added value: +{
      +  "description": "Who may submit, for example 'PhD students only' or 'Open to everyone'; empty when not checked.",
      +  "title": "Who May Submit",
      +  "type": "string"
      +}
    • changedOutput schema / $defs / EventMetadata / required
      Previous value: -[
      -  "series_name",
      -  "series_url",
      -  "event_type",
      -  "start_date",
      -  "end_date",
      -  "location",
      -  "official_url",
      -  "source_urls",
      -  "categories",
      -  "deadlines",
      -  "calendars"
      -]New value: +[
      +  "series_name",
      +  "series_url",
      +  "event_type",
      +  "start_date",
      +  "end_date",
      +  "location",
      +  "official_url",
      +  "source_urls",
      +  "categories",
      +  "deadlines",
      +  "calendars",
      +  "who_may_submit",
      +  "eligibility",
      +  "submission",
      +  "submission_checked_on",
      +  "submission_ready"
      +]
  2. First observed

TDQS

A3.6/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 covered elsewhere. The description adds the meaningful qualifier 'public' facts, signaling that only publicly exposed fields are returned, but it does not address behavior for unknown ids, errors, or pagination.

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?

It is a single front-loaded sentence with no filler, and the enumerated return fields are informative rather than decorative. The field list is somewhat long, but each item conveys what the agent can expect to receive.

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?

For a one-parameter, read-only, idempotent lookup with a full output schema and complete annotation coverage, the definition supplies everything needed to invoke it correctly. The field enumeration is mildly redundant given the output schema, but it does not create gaps.

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 coverage is 100% and the single 'id' parameter is already documented as 'Event id from search' with a pattern constraint. The description restates that the id comes from search without adding format, validity, or failure semantics beyond the schema, so the baseline of 3 applies.

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 names a specific verb ('Get'), a specific resource ('the public facts of one event'), the lookup key ('by its id'), and enumerates the returned fields (dates, location, deadlines, URLs, calendar feeds). That is enough for an agent to tell it apart from search, list_calendars, and list_upcoming_deadlines, though it does not explicitly name those siblings as alternatives.

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?

The phrase 'by its id from search' implies the prerequisite workflow: the agent must first obtain an id via search before calling this tool. However, there is no explicit when-to-use/when-not statement or named alternative for retrieving event data, so the guidance is only implied.

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