Skip to main content
Glama
Sign In
devto-mcp

devto-mcp

by AhmadTariq1337
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get my Dev.to profile

devto_get_profile

Retrieve profile information for the authenticated Dev.to account, including username, bio, and profile picture.

Instructions

Get the authenticated account's profile info.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devto_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It discloses a read operation and the requirement for authentication, but does not describe the response structure or behavior on failure. For a simple read-only tool, this is minimal but sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, straightforward sentence that fully conveys the tool's purpose. It is concise and front-loaded, with no unnecessary words or repetition.

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?

There is no output schema, so the description could ideally explain what 'profile info' includes. However, the tool's low complexity (zero parameters, simple read operation) makes the current description nearly complete, with only minor ambiguity about return fields.

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?

The tool has zero parameters, and the schema coverage is effectively complete (empty properties). The baseline for no parameters is 4; the description adds nothing further because there are no parameters to clarify.

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?

The description clearly states the tool retrieves the authenticated account's profile info, using a specific verb ('Get') and resource ('profile'). It distinguishes from sibling tools that focus on articles and comments, and the title reinforces the 'my profile' scope.

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?

No explicit usage guidance or comparisons to alternatives are provided. The intended use is implied by the tool's name and description, but it does not state when to use this tool versus the sibling tools.

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