Skip to main content
Glama
ssm82

Full VK MCP

vk_friends_are_friends

Check if the current VK user is friends with specified user IDs. Optionally return sign field or extended read state.

Instructions

Checks the current user's friendship status with other specified users. VK API method: friends.areFriends. Tool name: vk_friends_are_friends. Section: friends. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idsYesIDs of the users whose friendship status to check.
need_signNo'1' - to return 'sign' field. 'sign' is md5("{id}_{user_id}_{friends_status}_{application_secret}"), where id is current user ID. This field allows to check that data has not been modified by the client. By default: '0'.
extendedNoReturn friend request read_state field
Behavior4/5

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

The description mentions 'Access level: read', indicating a safe read operation. No annotations are provided, so this fills the gap. No side effects or rate limits are mentioned, but the read hint suffices.

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?

The description is concise with one functional sentence plus technical metadata. The metadata is somewhat redundant but not excessive.

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?

No output schema exists, but the description fails to mention return value structure (e.g., friend status codes). Schema descriptions cover parameters well, but overall completeness is moderate.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's own descriptions for user_ids, need_sign, and extended.

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 checks friendship status with specified users, using a specific verb 'checks' and resource 'friendship status'. It distinguishes from siblings by specifying 'with other specified users', implying targeted queries rather than listing all friends.

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?

The description does not explicitly state when to use this tool over alternatives. It implies usage for checking specific user statuses but lacks direct guidance or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ssm82/full-vk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server