Fetch a single Discord entitlement by providing the application ID and entitlement ID, returning its full details.
Purpose: Fetch a single entitlement.
Returns: entitlement shape.
| Name | Required | Description | Default |
|---|---|---|---|
| application_id | Yes | Your application/bot ID | |
| entitlement_id | Yes | Entitlement to fetch |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.28.0Output schema / anyOfPrevious value: -[
- {
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "additionalProperties": {},
- "properties": {
- "application_id": {
- "description": "Discord application ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- "consumed": {
- "type": "boolean"
- },
- "deleted": {
- "type": "boolean"
- },
- "ends_at": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "guild_id": {
- "anyOf": [
- {
- "description": "Discord guild (server) ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "id": {
- "description": "Discord entitlement ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- "sku_id": {
- "description": "Discord SKU ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- "starts_at": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "type": {
- "maximum": 9007199254740991,
- "minimum": -9007199254740991,
- "type": "integer"
- },
- "user_id": {
- "description": "Discord user ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- }
- },
- "required": [
- "id",
- "sku_id",
- "application_id",
- "type",
- "deleted"
- ],
- "type": "object"
- },
- {
- "properties": {
- "category": {
- "enum": [
- "client",
- "server"
- ],
- "type": "string"
- },
- "code": {
- "type": "string"
- },
- "recovery_hint": {
- "type": "string"
- },
- "retriable": {
- "type": "boolean"
- }
- },
- "required": [
- "code",
- "retriable",
- "category",
- "recovery_hint"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "application_id": {
+ "description": "Discord application ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ "consumed": {
+ "type": "boolean"
+ },
+ "deleted": {
+ "type": "boolean"
+ },
+ "ends_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "guild_id": {
+ "anyOf": [
+ {
+ "description": "Discord guild (server) ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "description": "Discord entitlement ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ "sku_id": {
+ "description": "Discord SKU ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ "starts_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "type": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "user_id": {
+ "description": "Discord user ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "sku_id",
+ "application_id",
+ "type",
+ "deleted"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "category": {
+ "enum": [
+ "client",
+ "server"
+ ],
+ "type": "string"
+ },
+ "code": {
+ "type": "string"
+ },
+ "recovery_hint": {
+ "type": "string"
+ },
+ "retriable": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "code",
+ "retriable",
+ "category",
+ "recovery_hint"
+ ],
+ "type": "object"
+ }
+]v0.22.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare the tool as read-only, open-world, idempotent, and non-destructive. The description adds only 'Returns: entitlement shape' which is minimal and redundant with the output schema. It does not disclose any additional behavioral traits such as error conditions, permission requirements, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two short sentences, front-loading the purpose and then noting the return value. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (two parameters, output schema provided), the description is adequate but sparse. It does not mention any context about when to use this over other entitlement tools, but for a simple fetch it may be sufficient. However, it lacks any note about potential errors or the fact that it's a read operation, though annotations cover that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes both parameters with high coverage (100%). The description does not add any additional semantic meaning beyond what the schema provides. It simply references the tool's purpose without explaining parameter usage or formats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Fetch a single entitlement' with a specific verb and resource, and 'single' distinguishes it from the 'entitlements_list' sibling which would fetch multiple. It also differentiates from consume/create/delete tools by the fetch action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like entitlements_list or entitlements_consume. It does not mention any prerequisites or exclusions. An agent would have to infer usage from the name and parameters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.