Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord application

discord_application_get
Read-onlyIdempotent

Retrieve a public Discord application record by application ID, including app-directory details when the application is discoverable.

Instructions

Get a public Discord application record, with its app-directory detail when the application is discoverable. Requires applicationId.

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

Input Schema

NameRequiredDescriptionDefault
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.
applicationIdYesRequired. Application id, 1 to 20 digits and at most 9223372036854775807, e.g. `936929561302675456`.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description contributes the notable behavioral facts that only public applications are returned and that app-directory detail appears conditionally on discoverability, but says nothing about failures for unknown or non-public IDs.

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 outcome and followed by the conditional return detail. The trailing 'Requires `applicationId`' is redundant with the schema's required list, which is the only wasted clause.

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 single-resource read tool with full schema coverage, high-quality annotations and no output schema, the description supplies what the structured fields cannot: the public-only constraint and the conditional directory payload. Nothing an agent needs to call it correctly is absent.

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 all four parameters are documented in the schema itself, including the context/llm_model/conversation_id protocol fields. The description only restates that applicationId is required, adding no meaning beyond the structured field.

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?

Names a specific verb and resource ('Get a public Discord application record') and adds scope ('app-directory detail when discoverable'). It is clearly distinguishable from list-type siblings like discord_applications_index_list, though it never names an alternative explicitly.

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 is only implied by the word 'public' and the applicationId prerequisite; there is no statement of when to prefer this over discord_application_similar_list or the applications index list, nor any exclusion condition.

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