Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to events

dev_to_events_list
Read-onlyIdempotent

Retrieves Dev.to challenges, live streams, and community events, optionally filtered by event type, so you can discover current developer activities and programs.

Instructions

List Dev.to challenges, live streams and other events. Optional inputs: type. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly events of this type. Omit for all events.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds essentially nothing beyond 'Returns a list' — no pagination behavior, no rate-limit or auth notes, no indication of result ordering or freshness.

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?

Two short sentences, front-loaded with the resource being listed, with no filler prose. The 'Optional inputs: `type`. Returns a list.' clause is mildly redundant with the schema but costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only list tool with rich annotations and full schema coverage, so most burden is carried elsewhere. However, with no output schema, 'Returns a list' is the only return-value information and it does not say what an event record contains or how results are ordered or paginated.

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 the baseline is 3. The description repeats that `type` is optional and omits meaning for the required meta-parameters (context, llm_model, conversation_id), but those are thoroughly documented in the schema itself, so no added value is required.

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?

States a specific verb and resource ('List Dev.to challenges, live streams and other events'), and the enumeration of event types makes the scope concrete enough to distinguish it from sibling list tools like dev_to_articles_list or dev_to_videos_list. It stops short of naming any sibling or drawing an explicit boundary, so it lands at 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to an alternative tool. The only usage-adjacent statement is that `type` is optional, which is already conveyed by the schema.

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

Deploy Server

Other Tools