userUser profile(s) by handle (up to 10000 semicolon-separated).
| Name | Required | Description | Default |
|---|---|---|---|
| handles | Yes | 1-10000 handles |
| Name | Required | Description | Default |
|---|---|---|---|
| result | No | Array of user profile objects | |
| status | Yes | Response status (OK or FAILED) | |
| comment | No | Error comment (if status is FAILED) |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "handles": [
+ "tourist"
+ ]
+ },
+ {
+ "handles": [
+ "tourist",
+ "ecnerwala",
+ "Um_nik"
+ ]
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "comment": {
+ "description": "Error comment (if status is FAILED)",
+ "type": "string"
+ },
+ "result": {
+ "description": "Array of user profile objects",
+ "items": {
+ "properties": {
+ "avatar": {
+ "description": "Avatar URL",
+ "type": "string"
+ },
+ "city": {
+ "description": "City ID (if available)",
+ "type": "string"
+ },
+ "contribution": {
+ "description": "Contribution score",
+ "type": "number"
+ },
+ "country": {
+ "description": "Country ID (if available)",
+ "type": "string"
+ },
+ "email": {
+ "description": "User email (if available)",
+ "type": "string"
+ },
+ "firstName": {
+ "description": "First name (if available)",
+ "type": "string"
+ },
+ "friendOfCount": {
+ "description": "Number of users who friend this user",
+ "type": "number"
+ },
+ "handle": {
+ "description": "User handle",
+ "type": "string"
+ },
+ "lastName": {
+ "description": "Last name (if available)",
+ "type": "string"
+ },
+ "lastOnlineTimeSeconds": {
+ "description": "Unix timestamp of last online",
+ "type": "number"
+ },
+ "maxRank": {
+ "description": "Maximum rank achieved",
+ "type": "string"
+ },
+ "maxRating": {
+ "description": "Maximum rating achieved",
+ "type": "number"
+ },
+ "openVkId": {
+ "description": "Open VK ID (if available)",
+ "type": "string"
+ },
+ "organization": {
+ "description": "Organization (if available)",
+ "type": "string"
+ },
+ "rank": {
+ "description": "Current rank",
+ "type": "string"
+ },
+ "rating": {
+ "description": "Current rating (if rated)",
+ "type": "number"
+ },
+ "registrationTimeSeconds": {
+ "description": "Unix timestamp of registration",
+ "type": "number"
+ },
+ "titlePhoto": {
+ "description": "Title photo URL",
+ "type": "string"
+ },
+ "vkId": {
+ "description": "VK ID (if available)",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Response status (OK or FAILED)",
+ "type": "string"
+ }
+ },
+ "required": [
+ "status"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds the 'up to 10000' limit but no further behavioral context (e.g., data freshness, 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?
Extremely short, but 'profile(s)' is awkward and the semicolon mention is misleading. Could be clearer without increasing length.
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 output schema exists, basic completeness is achieved. However, lacks information on case sensitivity, profile fields returned, and relationship to sibling tools.
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?
Schema coverage is 100% but the description mentions 'semicolon-separated' while the schema uses an array, creating ambiguity. Does not clarify whether the API expects a string or array.
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 it retrieves user profiles by handle, and specifies the batch capability (up to 10000). It distinguishes from sibling tools by mentioning handles and semicolon separation, but could be more precise.
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?
No guidance on when to use this tool versus alternatives like 'entity_profile' or 'user_rating'. Missing context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.